Intuition What this page is for
The parent note showed why emergence happens: a smooth per-token skill p raised to a task length L (the quantity p L ) makes a downstream metric look like it jumps. This page makes you run that machine by hand across every case it can throw at you — small p , large p , the limits p → 0 and p → 1 , degenerate L = 1 , the "mirage" smooth metric, chained sub-skills, and even a case where scaling hurts .
Back-links for the ideas we lean on: Emergent abilities in large models (parent), Scaling laws (Kaplan, Chinchilla) , Cross-entropy loss and perplexity , Chain-of-thought prompting , In-context learning , Inverse scaling .
Before any symbol appears, here is the whole vocabulary, built from zero:
Definition The five symbols we will reuse (define once, use forever)
p = the probability that one single token (one "word-piece") of the answer is correct. A number between 0 and 1 . Think: "how good is the model at getting one step right?"
L = the number of tokens that must all be correct for the task to count as solved. A whole number (1 , 2 , 3 , … ). Think: "how long is the chain?"
N = the size of the model (parameters, as in Scaling laws (Kaplan, Chinchilla) ). Bigger N generally means bigger p . We use N whenever an example says "scale the model up" — that phrase means increase N , which nudges p upward.
Acc = exact-match accuracy = fraction of times the entire answer is right = p L (all L tokens correct, assuming each is independent). This is a harsh, all-or-nothing metric.
TokenScore = a smooth, forgiving metric = the expected number of correct tokens = L p . Unlike Acc it gives partial credit : getting 9 of 10 tokens right scores 9 , not 0 . We meet it properly in Ex 7.
The symbol p L means "p multiplied by itself L times". Because p < 1 , multiplying it by itself shrinks it — and that shrinking is the whole story of emergence. By contrast L p is just "p scaled up by L " — no shrinking, no drama.
Every worked example below fills one cell of this table. The columns are the case classes this topic can throw at you.
Cell
Case class
What is being stressed
Example
A
Low p (small model)
p L ≈ 0 — "looks impossible"
Ex 1
B
High p (large model)
p L jumps up — "suddenly solved"
Ex 2
C
Both endpoints together (the jump)
forecast the emergence gap
Ex 3 (figure)
D
Degenerate L = 1
single-token task never emerges
Ex 4
E
Limit p → 1
ceiling behaviour, why it saturates
Ex 5
F
Limit p → 0 / chance floor
why the curve sits flat at zero
Ex 6
G
Smooth-metric "mirage"
same model, no jump under a soft lens
Ex 7 (figure)
H
Chained sub-skills (p k , CoT)
composition, why steps can hurt
Ex 8
I
Real-world word problem
3-digit arithmetic, pick L yourself
Ex 9
J
Exam twist / inverse scaling
bigger model, worse score
Ex 10
We now walk them in order.
A small model (small N ) gets each token right with p = 0.60 on a task needing L = 15 tokens all correct. What exact-match accuracy do we expect?
Forecast (guess first): with p = 0.6 (which sounds "more than half right"), do you expect accuracy near 0.6 ? Near 0.3 ? Near 0 ?
Steps
Write the metric. Why this step? Exact-match needs every token right, and the tokens are treated as independent, so the probability of all L being right is the product p × p × ⋯ = p L .
Acc = p L = 0.6 0 15
Compute. Why this step? to feel how brutal the exponent is.
0.6 0 15 ≈ 0.00047
Interpret. Why? 0.6 sounds decent, but raised to the 15th power it is under 0.05% — indistinguishable from "can't do it at all". This is the flat floor of the emergence curve.
Verify: sanity check bounds. Since 0 < 0.6 < 1 , we must have 0 < 0. 6 15 < 0.6 , and indeed 0.00047 < 0.6 . ✓ The number is far below chance-visible levels.
The model is scaled up (larger N ) until per-token correctness reaches p = 0.97 on the same L = 15 task. What is the new exact-match accuracy?
Forecast: p went from 0.60 to 0.97 — a 37 -percentage-point per-token gain. Does accuracy also gain roughly 37 points, or far more?
Steps
Reuse the metric. Why? Nothing about the formula changed, only p (driven by the larger N ).
Acc = 0.9 7 15
Compute. Why? to compare against Ex 1.
0.9 7 15 ≈ 0.633
Interpret. Why? Accuracy leapt from 0.00047 to 0.63 — a ≈ 1300 × jump from a modest per-token improvement. This is what "emergent" looks like on a plot, yet the per-token skill moved smoothly.
Verify: bound check 0 < 0.9 7 15 < 0.97 holds (0.633 < 0.97 ). ✓ And Ex2 ≫ Ex1, consistent with 0.97 > 0.60 . ✓
Doubling parameters (N → 2 N ) moves p from 0.85 → 0.97 on a L = 30 task. Forecast the exact-match accuracy before and after, then measure the "emergence gap".
Forecast: guess both numbers and their ratio.
Figure below (what it shows): the horizontal axis is per-token correctness p running 0 to 1 ; the vertical axis is exact-match accuracy Acc = p L , also 0 to 1 . Two curves are drawn: a coral curve for L = 30 (the long chain) and a mint curve for L = 5 (a short chain). Two lavender dots mark the before-scale point ( 0.85 , 0.008 ) and after-scale point ( 0.97 , 0.40 ) , and a butter-yellow band between them is the emergence gap.
Steps
Before-scale accuracy. Why? this is the "small model" point on the curve.
Acc before = 0.8 5 30 ≈ 0.0076
After-scale accuracy. Why? the "large model" point.
Acc after = 0.9 7 30 ≈ 0.401
Emergence gap. Why? the visible "jump" is the difference (or ratio).
0.401 − 0.0076 ≈ 0.393 , 0.0076 0.401 ≈ 53 ×
Read the figure. Why this step? On the axes just described (both 0 to 1 ), the coral curve (L = 30 ) hugs the bottom axis for most of the p -range then rockets up between p = 0.85 and p = 0.97 — the butter-yellow shaded gap between the two lavender dots is the emergence. The mint curve (L = 5 ) climbs gently from the same axis: shorter chains emerge less sharply.
Verify: matches the parent note's own Forecast-then-Verify (0.8 5 30 ≈ 0.0076 , 0.9 7 30 ≈ 0.401 ). ✓
A task needs only a single token (L = 1 ) — e.g. answer "yes" or "no". Per-token skill rises p = 0.60 → 0.97 (as N grows). How sharp is the accuracy jump now?
Forecast: with the amplifier L = 1 , do we still get a dramatic jump?
Steps
Plug L = 1 . Why this step? L is the amplifier; setting it to 1 removes amplification.
Acc = p 1 = p
Evaluate endpoints. Why? to compare with the L = 30 case of Ex 3.
Acc before = 0.60 , Acc after = 0.97
Interpret. Why? accuracy just equals p — it improves as smoothly as p does. No emergence. This is the degenerate boundary of the whole phenomenon: single-token metrics never "look emergent" because there is nothing to raise to a big power.
Verify: 0.6 0 1 = 0.60 and 0.9 7 1 = 0.97 exactly; gap = 0.37 = the raw per-token gain. ✓ No amplification, as predicted.
A large model already sits at p = 0.99 on the L = 20 task. It is scaled again to p = 0.999 . How much accuracy is left to gain, and why does the curve flatten at the top?
Forecast: near-perfect per-token skill — is the remaining accuracy gain big or small?
Steps
Accuracy at p = 0.99 . Why? starting point near the ceiling.
0.9 9 20 ≈ 0.818
Accuracy at p = 0.999 . Why? to see the diminishing return.
0.99 9 20 ≈ 0.980
Limit reasoning. Why this step? As p → 1 , p L → 1 L = 1 . The curve saturates : once you are past the knee, further per-token gains buy less and less accuracy because you are running out of room below 1 .
lim p → 1 p L = 1
Interpret. Why? emergence is sharp in the middle, flat at both ends — an S-shape. The top flat part is this p → 1 saturation.
Verify: 0.9 9 20 ≈ 0.818 (matches parent note's number) and 0.99 9 20 ≈ 0.980 < 1 , gain ≈ 0.16 — small, confirming saturation. ✓
Explain, with numbers, why the accuracy curve sits dead flat near zero for a whole range of small-model sizes, on an L = 25 task, as p crawls from 0.10 to 0.30 .
Forecast: p tripled from 0.10 to 0.30 . Does accuracy triple?
Steps
Evaluate both. Why? to expose the floor.
0.1 0 25 = 1 0 − 25 , 0.3 0 25 ≈ 8.5 × 1 0 − 14
Compare to "visible on a plot". Why this step? Both are astronomically below any measurable accuracy (a benchmark has maybe thousands of examples, so anything under ∼ 1 0 − 4 reads as exactly 0 ).
Limit reasoning. Why? As p → 0 , p L → 0 L = 0 . For small p , p L is effectively zero for a long stretch of scale — this is the flat left arm of the S-curve. Progress is happening (from 1 0 − 25 to 1 0 − 14 , an eleven-order-of-magnitude gain!) but the harsh metric shows nothing.
lim p → 0 p L = 0
Interpret. Why? this is exactly the "small models tell us nothing" trap — under exact-match they look identical, though they differ enormously. Use a smooth metric (Ex 7) to see the difference.
Verify: 0.3 0 25 ≈ 8.5 × 1 0 − 14 , and it is vastly larger than 1 0 − 25 yet both round to 0 on any real benchmark. ✓
Take the exact p -values from Ex 3 (0.85 → 0.97 , L = 30 ). Instead of exact-match, score with the smooth metric TokenScore = L p (expected number of correct tokens, defined in the vocabulary block). Does emergence survive?
Forecast: will the smooth metric also show a sudden jump?
Figure below (what it shows): the horizontal axis is again per-token correctness p (0 to 1 ); the vertical axis is a normalised metric value on a shared 0 -to-1 scale. The lavender curve is exact-match p 30 (which leaps near p = 1 ); the mint straight line is TokenScore / L = p (a smooth diagonal). Dotted vertical guides sit at p = 0.85 and p = 0.97 , with coral dots on the lavender curve and butter-yellow dots on the mint line marking those two scales.
Steps
Compute the smooth metric before/after. Why this step? TokenScore = L p is linear in p — no exponent, no amplifier.
TokenScore before = 30 × 0.85 = 25.5
TokenScore after = 30 × 0.97 = 29.1
Compute the fractional change. Why? to compare "jump size" against the 53 × ratio of exact-match (Ex 3).
25.5 29.1 ≈ 1.14 ( a 14% rise )
Interpret. Why? Exact-match said 53 × ; the smooth metric says 1.14 × . Same model, same p — the jump was manufactured by the metric. This is the Schaeffer "mirage" argument made concrete.
Read the figure. Why? on the axes just described, the lavender exact-match curve leaps upward near the right edge; the mint TokenScore line is a gentle straight diagonal — between the two dotted guides it barely rises.
Verify: 30 × 0.85 = 25.5 and 30 × 0.97 = 29.1 exactly; ratio 29.1/25.5 ≈ 1.14 . ✓
Chain-of-thought prompting adds k = 8 reasoning steps, each with per-step success q . A small model has q = 0.55 ; a large model has q = 0.95 . Chain success is q k . Does adding the steps help or hurt each model?
Forecast: does decomposing the problem into 8 steps help the small model?
Steps
Small-model chain. Why this step? each extra step is another factor < 1 , multiplying the failure risk.
0.5 5 8 ≈ 0.0084
Large-model chain. Why? same formula, higher q .
0.9 5 8 ≈ 0.663
Compute the ratio. Why this step? to quantify how many times better the large model's chain is — the raw ratio is the honest measure of the gap, just like the emergence ratio in Ex 3.
0.5 5 8 0.9 5 8 = 0.0084 0.663 ≈ 79 ×
Compare & interpret. Why? the small model's 8-step chain collapses to under 1% — worse than it would do guessing a short answer — while the large model keeps 66% , a ≈ 79 × advantage. This is why CoT helps big models and hurts small ones — the composition penalty q k dominates until q is high.
Cross-link. Why? this is the same p L engine, now with k reasoning steps instead of L output tokens — see In-context learning where a latent task must be applied consistently.
Verify: 0.5 5 8 ≈ 0.0084 , 0.9 5 8 ≈ 0.663 ; the large chain is ≈ 79 × the small chain. ✓
A model does 3-digit addition (e.g. 472 + 385 = 857 ). The answer is 3 digit-tokens, and every digit including carries must be exactly right, so treat L = 3 . Per-digit correctness rises with scale (N ) from p = 0.70 to p = 0.98 . What accuracy is reported at each scale, and does this match the "0% then high" observation from the parent note?
Forecast: with only L = 3 , is the jump dramatic or mild?
Steps
Choose L . Why this step? the word problem requires you to model the task; a 3-digit sum needs 3 output digits all correct.
L = 3
Small-scale accuracy. Why? the "before" point.
0.7 0 3 = 0.343
Large-scale accuracy. Why? the "after" point.
0.9 8 3 ≈ 0.941
Interpret & reconcile. Why? Here the jump is real but milder (0.34 → 0.94 ) because L = 3 is small. Reported "∼ 0% then high" curves usually involve longer answers or more carries (effectively larger L ), which is why they look flatter-then-sharper. Match the sharpness to the chain length.
Verify: 0.7 0 3 = 0.343 exactly, 0.9 8 3 ≈ 0.941 ; and because L = 3 < 15 , the jump (≈ 2.7 × ) is far gentler than Ex 3's 53 × . ✓ Consistent with "longer chain ⇒ sharper emergence".
Worked example Statement (exam-style)
On some tasks the bigger model does worse — Inverse scaling . Suppose a bigger model (larger N ) learns a tempting wrong pattern , so its per-token correctness actually drops from p = 0.90 (small) to p = 0.75 (large) on an L = 10 task. What happens to exact-match accuracy, and does p L still explain the shape?
Forecast: if p drops from 0.90 to 0.75 , is the accuracy drop mild or amplified?
Steps
Small-model accuracy. Why this step? baseline before the harmful scaling.
0.9 0 10 ≈ 0.349
Large-model accuracy. Why? after the harmful pattern is learned.
0.7 5 10 ≈ 0.056
Compute the drop ratio. Why? to measure how much the amplifier magnifies the regression.
0.7 5 10 0.9 0 10 = 0.056 0.349 ≈ 6.2 ×
Interpret. Why? The p L amplifier works in both directions: a 0.90 → 0.75 per-token drop becomes a 0.349 → 0.056 collapse (a ≈ 6.2 × fall). So the same machinery that makes good improvements look emergent makes bad regressions look like sudden failures — this is why inverse scaling can also appear abrupt.
Reconcile with the parent note. Why? it warned "bigger is not always suddenly better"; this is the concrete counterexample.
Verify: 0.9 0 10 ≈ 0.349 , 0.7 5 10 ≈ 0.056 ; drop ratio ≈ 6.2 × . Amplification is symmetric, as claimed. ✓
Recall Which matrix cell never shows emergence, and why?
Cell D (L = 1 ) ::: With a single required token, accuracy = p 1 = p , so it tracks per-token skill smoothly — nothing is raised to a big power, so no amplification, no jump.
Recall Same
p shift (0.85 → 0.97 ): why 53 × under exact-match but only 1.14 × under TokenScore?
Exact-match is p L (non-linear amplifier) while TokenScore is L p (linear). ::: The metric, not the model, creates the apparent jump — the "mirage".
Recall What does the
p → 0 limit tell us about small models?
p L → 0 , so a wide band of small models all read as 0% under exact-match even though their true p differs by many orders of magnitude — use a smooth metric to see the real trend.
Mnemonic One line to keep
"p L amplifies — up (emergence), flat (mirage), and down (inverse scaling)." Choose L from the task, and the shape follows.