“Next-token predictor” is the wrong mental model for LLMs
TL;DR Highlight
RLVR trains LLMs to maximize reward, not predict data tokens, so next-token predictor is incomplete.
Who Should Read
A developer using LLM APIs who is unsure whether 'just a next-token predictor' is an accurate way to describe LLMs.
Core Mechanics
- Inference still emits tokens one at a time
- At generation time the loop does look like a next-token predictor.
- The author says the claim is not wrong, just incomplete.
- Pre-training really is next-token prediction
- It raises the probability of the token that actually followed in the training data.
- So the base model can be called a next-token predictor.
- RLVR has no correct next token to predict
- RLVR is reinforcement learning with verifiable rewards.
- Tokens in sequences the model generated itself become more likely when those sequences earn high reward.
- Same function, different reason
- Pre-training raises a token's probability because it appeared in the data.
- RLVR raises it because the sequence containing it earned a high reward.
- A chess engine illustrates the gap
Community Reactions
- Counterpoint that it is still prediction
- One commenter argued what is learned is still P(token_k | previous tokens).
- In their view where it was learned from does not change the task.
- Opinion that pre-training is not plain next-token prediction either
- A commenter noted backprop sums loss contributions from all later tokens into each position's representation.
- So representations are not optimized only for the next token.
- Experience that the next-token model explains real errors
- A commenter saw 'schmuck' output for 'schmutz' and answers locked in by an early 'Yes' that later got contradicted.
- They said the next-token model explained both.
- Opinion that the chess analogy is weak
- A commenter noted chess engines pick a whole branch from a search tree.
- They said no one has explained where a transformer stores a future plan.
- Opinion that the right model depends on context
How to Apply
- Sort model failures into two layers
- Pick 3 failing prompts today and label each as early-token lock-in or failed reward-style problem solving.
- If the first answer is wrong, reorder so the model writes reasoning before the answer and rerun.
- Reorder prompts to put the conclusion last
- In Yes/No judgment prompts, require reasoning first and the verdict at the end.
- Compare on the same inputs to see whether early tokens stop fixing the answer.
- Attach a result verifier to checkable tasks
- For code or math, run tests and feed pass/fail back to the model for retries.
- This mirrors how RLVR uses pass/fail as the reward.
Try It
# Paste into Claude or ChatGPT (simplified version of the paper's method: mimicking a verified reward)
You are a solver for the problem below. Solve it with 3 different approaches, then score each solution 0-10 using a verifiable criterion (tests or recomputation).
Problem: {{problem}}
Rules: put the conclusion only at the very end; write the reasoning and verification first. Choose the highest-scoring solution as the final answer.
Next to try: ask the same problem with "state the conclusion first" and compare accuracy.Terminology
Related Papers
AI is a tool and using it well takes skill
A rebuttal to Hickey: LLMs are tools, and skill in directing and checking them decides the outcome
Reflective Prompt Optimization of a Deep-Research Agent: A Topic-Disjoint, Multi-Seed Protocol for Measuring Transferable Gains and Prompt-Level Overfitting
Reflective prompt optimization raised held-out citation reward from 0.702 to 0.781 on a deep-research agent.
GPT‑6 and Intelligent UI for everyone
GPT-6 reportedly adds generated UI to chat; with no article text, only comment reactions are available.
Base Models Can Reason By Taking a Cue From Training Data
Prefilling just two opening tokens lifted Olmo-3-7B's MATH-500 accuracy from 42% to 78%.
Labels Override Definitions in Jev-Style Typed Decision Models
Renaming options to A/B raised routing accuracy by +0.1511 over meaningful labels.
How Much Prompt Is Enough? A Blackbox Minimization of Few-Shots in LLMs
Delta debugging trimmed few-shot prompts by 65.3% on average with unchanged propositional output