IN THIS BREAKDOWN · 10 SECTIONS
You can read 17% of this breakdown.
The paper in one minute
In 2020 the standard recipe for a language task was to take a pre-trained model and fine-tune it on thousands of labeled examples of that one task. A new task meant a new dataset and a new model. People do not work that way. Show a person one or two examples and a sentence of instructions and they usually get it.
OpenAI asked whether a big enough language model could do the same. They trained GPT-3, a decoder-only Transformer with 175 billion parameters, on 300 billion tokens of web text, books and Wikipedia, and then never fine-tuned it. Every task was given to the model as text: an instruction, sometimes a handful of solved examples, then the case to solve. They called this in-context learning, and named three settings by how many examples the prompt contains: zero-shot, one-shot and few-shot.
The results moved the field. On closed-book TriviaQA, GPT-3 went from 64.3% zero-shot to 71.2% few-shot, the best published result for that setting in 2020, ahead of fine-tuned systems. On SuperGLUE, 32 examples per task in the prompt beat a BERT-Large model fine-tuned on 125,000. Small models could barely do any of this; the ability grew with size.
The paper is also unusually frank about where it failed, and those failures are as useful as the wins. Almost every LLM product since starts from its premise: describe the task in the prompt.
Research notes: the problem, approach and results
ten times larger than any previous non-sparse language model
per SuperGLUE task in the prompt, beating BERT-Large fine-tuned on 125,000
human accuracy at spotting GPT-3's news articles, against 50% for a coin toss
Every new language task needed its own labeled dataset of thousands of examples and its own fine-tuned model.
Scale a plain next-token predictor to 175 billion parameters and describe the task in the prompt, with zero, one or a few examples.
Strong results across dozens of benchmarks with no task-specific training, and a new way of building with models: prompting.
Why it matters to an FDE
This paper defines the first decision on almost every engagement: do we prompt, or do we train? It names the spectrum. Fine-tuning changes weights with thousands of examples. Few-shot puts 10 to 100 examples in the prompt. Zero-shot gives only an instruction. It also states the trade-off plainly: few-shot needs far less data, but it was then "much worse than state-of-the-art fine-tuned models" on many tasks.
Two findings matter more on a deployment than the headline scores.
Comparing two texts was a blind spot. GPT-3 scored 49.4% on WiC, a two-way choice where chance is 50%, and was near chance on ANLI. Both ask whether two pieces of text mean the same thing or whether one implies the other. That is exactly the shape of many enterprise asks: does this clause match our policy, does this invoice match the purchase order. Modern models are far stronger, but this is still the task type to test hardest before promising anything.
More examples is not always better. On the LAMBADA benchmark, one-shot accuracy (72.5%) came in below zero-shot (76.2%), though the paper notes zero-shot used a different prompt format. Prompt design is an experiment, not a formula, and each example you add costs tokens on every request.
Understand the mechanism. Try it on a real problem.
Unlock this breakdown and 49 more papers.
Premium opens every paper in full, plus every answer, concept, course and guide on the site. One payment for six months of access.
6 months · One payment · No auto-renewal
- ◇1 architecture diagram
- </>1 runnable code experiment
- ▦3 results tables
- ?5 interview questions with answers
- 03Key takeaways
The ideas to keep, the cost of examples worked out, the training mix and the misreadings to avoid
Free account - 04How it works
The model, the data, the evaluation protocol and why scale changes the picture, with a diagram
Premium - 05The numbers that matter
The results that matter for building, including the weak spots and the cost of training
Premium - 06Try it yourself
A harness that measures what each extra example costs, and the baseline your prompt must beat
Premium - 07Where it breaks
The limits the authors listed themselves, and what changed after the paper
Premium - 08Using it on a deployment
A decision procedure for prompt versus fine-tune, and how to test a prompt properly
Premium - 09Interview angles
Five questions this paper prepares you for, with answer hints
Premium - 10Read next
Where to go from here on this site
Premium
