Live data from Hacker News

Demo of =GPT3() as a spreadsheet feature

twitter.com

131–140 of 149 posts

Re: Demo of =GPT3() as a spreadsheet feature

#131

This seems to be doing much worse than existing solutions: Google Maps probably wouldn't have gotten quite as many wrong if you just pasted those addresses into the search bar. However it could be interesting as a last shot if parsing the input failed using any other way. "I tried parsing your messy input. Here's what I came up with. Please make sure it's correct then proceed with the checkout."

No post body was provided.

Re: Demo of =GPT3() as a spreadsheet feature

#132
post #90
post #81

The most sensible use for AI that I can see at this time is for supporting humans in their work, but only where the system is set up so that the human has to do the work first, with the AI system looking for possible errors. For example the human drives the car, and the AI brakes when it senses dangerous conditions ahead, or the human screens test results for evidence of cancer and the AI flags where it disagrees so…

Humans are also less than perfect systems. Especially if they have to deal with monotonous tasks. A human might perform better on a 100 entries than an AI, but on 10 thousand? Of course you can distribute the workload, but you will balloon the costs (I'm talking about a future where GPT3 costs come down). There must be a set of projects which are cost prohibited now due to having to pay humans but will become feasibl…

> A human might perform better on a 100 entries than an AI, but on 10 thousand?

There's also increased variance in human accuracy. You might train 100 but 10k people? A model is consistent all the way.

Re: Demo of =GPT3() as a spreadsheet feature

#133
post #70
post #46

Do I understand that correctly? When I have to create a spreadsheet like this, there are 2 options. Option 1 I write a table zipcode to state and use this table to generate my column. If I carefully check my table my spreadsheet would be okay. Option 2 I ask GPT3 to do my work. But I have to check the whole spreadsheet for errors.

I dealt with something similar. I was creating a large directory of childcare centres in Canada. I had thousands of listings with a url but no email address. I created a Mechanical Turk job to ask turkers to go to website and find an email address. Many came back with email addresses like admin@ >.com. After checking a few, I realized that the turkers were just guessing that admin@ would work and I'd approve their wo…

> I ended up having to double check all the work.

Me too, different project and different labelling company but the conclusion - it's better to do it in house. Labelling is hard. You need to see, talk with and train your labelling team.

Re: Demo of =GPT3() as a spreadsheet feature

#134

GPT3 charges for every token read/written. What may be more useful is using GPT-3 not to manually run itself on every row, but to take the task and generate a sufficient function that fulfills the task.

Code as Policies: - Language Model Programs for Embodied Control

generates python, then executes

https://code-as-policies.github.io/

Re: Demo of =GPT3() as a spreadsheet feature

#137
post #87
post #14

Of all the places spreadsheet is probably the one place you don’t want AI generated content. Half the time it’s financial info so sorta correct simply isn’t good enough

Spreadsheets are used for _waaaay_ more than just finances. I don't think it's anywhere near 50% finances. I can't recall where, but I saw a study from I think the 90s saying most of the spreadsheets they found were being used as Todo lists. Maybe like 1 in my past 2y of many, many spreadsheets has been financing related. I think you might be overgeneralizing to an ungeneralizeably large group -- the set of all human…

It does not matter the point stands. I can think of almost nothing worse than data in spreadsheets that LOOKS good but is wrong.

Re: Demo of =GPT3() as a spreadsheet feature

#138
post #11

The ability of language models to do zero-shot tasks like this is cool and all, but there is no way you should actually be doing something like this on data you care about. Like think about how much compute is going into trying to autofill a handful of zip codes, and you're still getting a bunch of them wrong.

yeah, determining the zip for an address is a really bad example. Better one would be "based on these three columns, generate a cold outbound email for the person..." it would suck to be on the receiving end of those, but the use case makes much more sense.

I've been wondering about this... It definitely doesn't feel great to be on the receiving end of something auto-generated. But a "unique" message is at least more interesting to read, and doesn't feel quite as frustrating.

A yet if P(someone unknown is a robot) gets too large, it's going to be a weird adjustment period.

Re: Demo of =GPT3() as a spreadsheet feature

#140
post #70
post #46

Do I understand that correctly? When I have to create a spreadsheet like this, there are 2 options. Option 1 I write a table zipcode to state and use this table to generate my column. If I carefully check my table my spreadsheet would be okay. Option 2 I ask GPT3 to do my work. But I have to check the whole spreadsheet for errors.

I dealt with something similar. I was creating a large directory of childcare centres in Canada. I had thousands of listings with a url but no email address. I created a Mechanical Turk job to ask turkers to go to website and find an email address. Many came back with email addresses like admin@ >.com. After checking a few, I realized that the turkers were just guessing that admin@ would work and I'd approve their wo…

That’s why you always set up layers of work with mturk, with other layers validating the first ones. Or give the same task to multiple workers and compare the results.
Post reply on HN