News for hackers. Stuff that matters.
Re:The Inherent Limitations of GPT-3 by PaulHoule on Monday November 29, 2021 @01:56PM (#29383677)
Works to accomplish what useful task?
Re:The Inherent Limitations of GPT-3 by Jack000 on Monday November 29, 2021 @02:34PM (#29384153)
I think it's better to think of GPT-3 not as a model but a dataset that you can interact with.

Just to give an example - recently I needed to get static word embeddings for related keywords. If you use glove or fasttext, the closest words for "hot" would include "cold", because these embeddings capture the context these words appear in and not their semantic meaning.

To train static embeddings that better captures semantic meaning, you'd need a dataset that would group words together like "hot" and "warm", "cold" and "cool" etc. exhaustively across most words in the dictionary. So I generated this dataset with GPT-3 and the resulting vectors are pretty good.

More generally you can do this for any task where data is hard to come by or require human curation.

Re:The Inherent Limitations of GPT-3 by andreyk on Monday November 29, 2021 @02:09PM (#29383839)
OpenAI has a blog post highlighting many (edit, not many, just a few) applications - https://openai.com/blog/gpt-3-apps/

It's quite powerful and has many cool uses IMHO.

Re:The Inherent Limitations of GPT-3 by PaulHoule on Monday November 29, 2021 @02:15PM (#29383918)
That post lists 3 applications, which is not enough to be "many". No live demos.

I don't know what Google uses to make "question answering" replies to searches on Google but it is not to hard to find cases where the answers are brain dead and nobody gets excited by it.

Re:The Inherent Limitations of GPT-3 by moron4hire on Monday November 29, 2021 @02:32PM (#29384129)
Yeah, 1 is "a", 2 is "a couple", 3 is "a few", 4 is "some". You don't get to "many" until at least 5, though I'd probably call it "a handful", 6 as "a half dozen", and leave "many" to 7+.
Re:The Inherent Limitations of GPT-3 by notreallyserio on Monday November 29, 2021 @02:43PM (#29384272)
I'm not so sure. Are these the definitions GPT-3 uses?
Re:The Inherent Limitations of GPT-3 by andreyk on Monday November 29, 2021 @02:50PM (#29384353)
That's fair , I forgot how many they had vs just saying it is powering 300 apps. There is also http://gpt3demos.com/ with lots of live demos and varied things, though it's more noisy.
Re:The Inherent Limitations of GPT-3 by beepbooptheory on Monday November 29, 2021 @02:52PM (#29384373)
Three is not "many" but this is still a pretty uncharitable response. Be sure to check the Guidelines.
Re:The Inherent Limitations of GPT-3 by jcims on Monday November 29, 2021 @02:27PM (#29384068)
I keep wondering if you can perform psychology experiments on it that would be useful for humans.
Re:The Inherent Limitations of GPT-3 by modeless on Monday November 29, 2021 @02:05PM (#29383794)
Github Copilot? It may not be perfect but I think it can definitely be useful.
Re:The Inherent Limitations of GPT-3 by PaulHoule on Monday November 29, 2021 @02:12PM (#29383887)
It is useful if you don't care if the product is right.

Most engineering managers would think "this is great!" but the customer won't agree. The CEO will agree until the customers revolt.

Re:The Inherent Limitations of GPT-3 by rpedela on Monday November 29, 2021 @03:04PM (#29384525)
There are several use cases where ML can help even if it isn't perfect or even just better than random. Here is one example in NLP/search.

Let's say you have a product search engine and you analyzed the logged queries. What you find is a very long tail of queries that are only searched once or twice. In most cases, the queries are either misspellings, synonyms that aren't in the product text, or long queries that describe the product with generic keywords. And the queries either return zero results or junk.

If text classification for the product category is applied to these long tail queries, then the search results will improve and likely yield a boost in sales because users can find what they searched for. Even if the model is only 60% accurate, it will still help because more queries are returning useful results than before. However you don't apply ML with 60% accuracy to your top N queries because it could ruin the results and reduce sales.

Knowing when to use ML is just as important as improving its accuracy.

Re:The Inherent Limitations of GPT-3 by PaulHoule on Monday November 29, 2021 @03:22PM (#29384739)
I am not against ML. I have built useful ML models.

I am against GPT-3.

For that matter I was interested in AGI 7 years before it got ‘cool’. Back then I was called a crackpot, now I say the people at lesswrong are crackpots.

Re:The Inherent Limitations of GPT-3 by chaxor on Monday November 29, 2021 @03:35PM (#29384906)
It's strange how HN seems to think that by religiously disagreeing with any progress which is labeled "ML progress" they are somehow displaying their technical knowledge. I don't think this is really useful, and the arguments often have wrong assumptions baked within them. It would be nice to see this pseudo-intellectualism quieted with a more appropriate response to these advancements. For example, I would imagine that there would be a similar response of collective groan for the paper on pagerank so many years ago, but this has clearly provided utility today. Why is it so hard for us to recognize that even small adjustments to algorithms can yeild utility, and this property extends to ML as well?

As someone mentioned above, language models for embedding generation has improved dramatically with these newer MLM/GPT techniques, and even with improvement to F-score/auc/etc. for one use case can generate enormous utility.

Nay-saying really doesn't make you look intelligent.

Re:The Inherent Limitations of GPT-3 by PaulHoule on Monday November 29, 2021 @03:39PM (#29384964)
I have worked as an ML engineer.

I also have strong ethical feelings and have walked away from clients who wanted me to introduce methodologies (e.g. Word2Vec for a medical information system) where it was clear those methodologies would cause enough information loss that the product would not be accurate enough to put in front of customers.