IN THIS BREAKDOWN · 10 SECTIONS
You can read 20% of this breakdown.
The paper in one minute
The standard ways to get a small task model are fine-tuning on human labels or distillation: label unlabeled data with a big model and train on its labels. Both need lots of data to match the big model. This paper treats the big model as a source of reasoning, not just labels.
Step 1. Prompt the large model (540B PaLM) with about ten worked examples, each an input, a written rationale and a label, so that for every new input it writes a rationale and a label. For a word problem about carpeting a room, the rationale says area is length times width; the label is the expression.
Step 2. Train a small T5 model on two tasks over the same inputs. With the prefix [label] it learns to output the label; with [rationale] it learns to write the rationale. The loss is the label loss plus λ times the rationale loss. At inference only the label task runs, so the deployed model is as fast as any fine-tuned T5 and never needs the large model.
On four datasets (e-SNLI and ANLI for inference, CommonsenseQA, SVAMP word problems), the method beat standard fine-tuning and standard distillation at every data size and model size tested. It matched full-data fine-tuning with 12.5% of e-SNLI, 25% of ANLI, 75% of CQA and 80% of SVAMP. With human labels, T5 models from 220M to 11B beat PaLM's few-shot chain-of-thought on all four tasks; with only unlabeled data, on three of four. Putting rationale and label into one output sequence, instead of two tasks, sometimes did worse than no rationales.
Research notes: the problem, approach and results
share of e-SNLI's labeled data T5-220M needed with rationales to beat standard fine-tuning on all of it
accuracy points on ANLI from adding PaLM rationales to T5-220M fine-tuning (43.58 to 49.58)
how much smaller the 770M T5 is than the 540B PaLM it beat on ANLI and SVAMP with human labels
Teams prompt a huge model for a narrow task because a small model would need many labeled examples to match it. Serving the huge model costs memory and latency, and labeling data costs people.
Prompt the large model with a few worked examples so it writes a rationale and a label for each training input. Train a small model on two tasks with prefixes: predict the label, and generate the rationale. At inference, run only the label task.
Across four tasks, rationales let T5 models match full-data fine-tuning with 12.5% to 80% of the labels. A 770M T5 beat 540B PaLM's few-shot chain-of-thought on ANLI with 80% of the data, where standard fine-tuning never caught up. Training rationale and label as one output sequence was worse than two tasks.
Why it matters to an FDE
A common deployment pattern: a customer prompts a large API model for a classification, extraction or routing task, it works, and then the bill and the latency arrive at production volume. The fix is a small fine-tuned model, but the customer has few labels. This paper is the recipe for that move.
Rationales stretch scarce labels. The large model is already being called; asking it to explain its answer costs extra output tokens per example, once, at training time. In return the small model needs a fraction of the labeled data, and at inference it emits only the label, so serving cost does not change.
The gain depends on the task. Rationales added 6.0 points on ANLI, a hard inference task, but about 1 point on e-SNLI and CQA. On e-SNLI, plain fine-tuning of a 220M model already beat PaLM's few-shot accuracy by about 15 points. Check whether the task needs reasoning before paying for rationales.
The student can beat the teacher. On e-SNLI and others, students trained only on PaLM's labels and rationales scored above PaLM's own few-shot accuracy. A small specialist trained on many teacher outputs can average out teacher mistakes; an FDE should measure on gold labels rather than assume the teacher is the ceiling.
Understand the mechanism. Try it on a real problem.
Unlock this breakdown and 149 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
- ▦2 results tables
- ?5 interview questions with answers
- 03Key takeaways
How the data and size savings break down, which design choices mattered, and three misreadings
Free account - 04How it works
Prompting for rationales, the multi-task loss, the baselines, models and datasets
Premium - 05The numbers that matter
Ablation tables, data reductions, model-size comparisons and the teacher's own accuracy
Premium - 06Try it yourself
Recompute the reductions and gaps, then train a toy student with and without rationales
Premium - 07Where it breaks
Teacher errors, unreported settings, small test sets, model-family limits and slips
Premium - 08Using it on a deployment
Turning a prompted LLM workflow into a small fine-tuned model with rationale supervision
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
