Nisan Stiennon, Long Ouyang, Jeff Wu, Daniel M. Ziegler, Ryan Lowe, Chelsea Voss, Alec Radford, Dario Amodei, Paul Christiano
As language models become more powerful, training and evaluation are increasingly bottlenecked by the data and metrics used for a particular task. For example, summarization models are often trained to predict human reference summaries and evaluated using ROUGE, but both of these metrics are rough proxies for what we really care about—summary quality. In this work, we show that it is possible to significantly improve summary quality by training a model to optimize for human preferences. We collect a large, high-quality dataset of human comparisons between summaries, train a model to predict the human-preferred summary, and use that model as a reward function to fine-tune a summarization policy using reinforcement learning. We apply our method to a version of the TL;DR dataset of Reddit posts and find that our models significantly outperform both human reference summaries and much larger models fine-tuned with supervised learning alone. Our models also transfer to CNN/DM news articles, producing summaries nearly as good as the human reference without any news-specific fine-tuning. We conduct extensive analyses to understand our human feedback dataset and fine-tuned models. We establish that our reward model generalizes to new datasets, and that optimizing our reward model results in better summaries than optimizing ROUGE according to humans. We hope the evidence from our paper motivates machine learning researchers to pay closer attention to how their training loss affects the model behavior they actually want.
As language models become more powerful, training and evaluation are increasingly bottlenecked by the data and metrics u...
This abstract describes a fundamental shift in how we train and evaluate language models for text summarization. Instead of using traditional metrics (like ROUGE) that measure how closely a model's summary matches human-written references, the authors propose training models to directly optimize for what humans actually prefer. Think of it as moving from "does this look like the gold standard answer?" to "do humans think this is good?"
This is a significant methodological innovation because it addresses a critical gap: our training objectives (what we make models optimize for) don't necessarily align with our true goals (what actually produces better summaries in practice).
"As language models become more powerful, training and evaluation are increasingly bottlenecked by the data and metrics used for a particular task."
What this means: As models get better, improvements are no longer limited by model capacity—they're limited by:
"For example, summarization models are often trained to predict human reference summaries and evaluated using ROUGE, but both of these metrics are rough proxies for what we really care about—summary quality."
Let me unpack this carefully:
The traditional pipeline:
where represents n-grams (sequences of words), and the metric counts how many reference n-grams appear in the generated summary.
Why these are "rough proxies":
The core insight: Optimizing for ≠ Optimizing for actual summary quality.
The authors propose a three-step approach:
Instead of a fixed training target (reference summaries), you now have an adaptive target that learns what humans actually prefer. The reward model acts as a learned evaluation function.
Mathematical formulation (intuitive):
If we denote:
The reward model learns a function such that:
where is the sigmoid function (converts unbounded scores into probabilities). The model learns by maximizing the likelihood of observed human preferences.
Then, the summarization policy is fine-tuned using reinforcement learning to maximize , where denotes the expectation over generated summaries.
--- ## Part 3: Experimental Results ### Performance Claims > "We find that our models significantly outperform both human reference summaries and much larger models fine-tuned with supervised learning alone." **Key comparisons:** - ✓ vs. human-written reference summaries (the standard baseline) - ✓ vs. larger models trained only with supervised learning (traditional fine-tuning) ### Generalization to New Domains > "Our models also transfer to CNN/DM news articles, producing summaries nearly as good as the human reference without any news-specific fine-tuning." This is important: The reward model learned on Reddit data (TL;DR dataset) generalizes to news articles without retraining. This suggests the model learns something about **what humans value in summaries generally**, not just domain-specific patterns. ### Core Validation > "We establish that our reward model generalizes to new datasets, and that optimizing our reward model results in better summaries than optimizing ROUGE according to humans." This directly confirms the paper's premise: When humans evaluate summaries, they prefer ones optimized for the learned reward model over those optimized for ROUGE. --- ## Part 4: What This Means (The Broader Impact) > "We hope the evidence from our paper motivates machine learning researchers to pay closer attention to how their training loss affects the model behavior they actually want." **The meta-lesson**: There's a critical distinction between: \text{Training objective} \quad \text{vs.} \quad \text{Actual goal}Models trained to minimize (ROUGE-based loss) don't necessarily maximize human satisfaction. This paper demonstrates that:
| Aspect | Traditional Approach | This Paper's Approach |
|---|---|---|
| Training Target | Static human reference summaries | Learned reward model from preferences |
| Evaluation Metric | ROUGE score | Human preference prediction |
| Optimization | Supervised learning on references | Reinforcement learning on reward |
| Result | Good ROUGE, mediocre actual quality | Lower ROUGE, better actual quality |
The abstract establishes that human preferences are a better target than proxy metrics, and demonstrates that this can be implemented practically through a reward model trained on human comparisons. This is the conceptual foundation for the rest of the paper.
Large-scale language model pretraining has become increasingly prevalent for achieving high performance on a variety of ...
This introduction sets up the core tension of the entire paper. The authors are saying: "We train language models one way, but we actually care about a completely different thing."
Think of it like this: imagine training a chess AI by just copying grandmaster games move-by-move (supervised learning). But what you really want is an AI that wins games. These aren't the same objective! The introduction explains why this mismatch happens and proposes their solution.
Currently, the field uses supervised learning on pretrained language models. Here's what that means mathematically:
Let me break down each part:
The authors identify three key problems:
Problem 1: No distinction between error types
Problem 2: Models learn from all demonstrations equally
Problem 3: Distribution shift during inference
The authors propose using human preferences as the training signal instead of just copying demonstrations. Here's the three-step approach:
Instead of collecting only reference summaries, collect pairwise comparisons:
Where:
This is more aligned with what we care about: which summary is actually better, not just whether it matches some particular reference wording.
Train a supervised model to predict human preferences:
The reward model (RM) learns , a function that assigns a quality score to any summary.
Now train the summarization policy using reinforcement learning to maximize the reward:
Where:
The authors use PPO (Proximal Policy Optimization), a standard RL algorithm that updates the policy based on the reward signal from entire summaries, not individual words.
The authors make an important philosophical point: this is about AI alignment.
In summarization, mistakes are low-risk (a made-up fact is obvious). But as AI systems get more powerful and handle critical tasks (medical diagnosis, financial advice, military decisions), subtle mistakes become dangerous. By developing methods to train on what humans actually prefer rather than what's easy to measure automatically, we're building better tools for the future.
The core insight is:
By introducing a reward model trained on human preferences, they bridge this gap:
This is the conceptual foundation for everything that follows in the paper.
Most directly related to our work is previous work using human feedback to train summarization models with RL. Bohm et a...
Before diving into their own methodology, the authors are doing what good researchers do: situating their work within the broader landscape of existing research. This section accomplishes three things:
For this paper on learning to summarize from human feedback, the authors need to show:
The authors mention three key prior works:
These are the two most directly related papers. Let's understand what each did:
Böhm et al.'s approach:
Reference [73]'s approach (also training on human feedback for summarization):
How the current paper differs from [73]:
The authors explicitly list their improvements:
The last point deserves clarification: in RL, the value network estimates expected future rewards, while the policy network decides what action to take. Separating them (rather than having one network do both) often leads to more stable and better training in practice. Think of it as having specialized experts rather than one generalist.
The authors then expand the scope, noting human feedback has been used successfully in many NLP domains:
The key insight: Human feedback as a training signal isn't novel to summarization. It's a general principle that works across multiple tasks.
This is an important conceptual bridge. The authors mention their reward modeling approach comes from prior work on learning to rank.
What is learning to rank?
In search engines, the goal is to rank documents by relevance. The problem can be formalized as:
Given a query and a set of documents , learn a function that assigns relevance scores such that:
The training data comes from:
Connection to this paper:
Instead of ranking documents, we're ranking summaries. The same mathematical framework applies:
The authors trained their reward model (where is the original document and is a summary) in exactly this ranking framework – they learned to predict which of two summaries humans prefer.
The section also mentions prior work applying RL to optimize automatic metrics (ROUGE, BLEU, etc.).
What does "optimizing automatic metrics with RL" mean?
Normally, ROUGE is just an evaluation metric – you compute it after training. But you could use it as a reward signal during training:
where:
Then train a policy to maximize:
Why mention this?
It shows there's a history of using RL in summarization. But the authors argue their approach is better because they're optimizing a learned reward model (trained on human preferences) rather than optimizing ROUGE directly (a flawed metric). This is a key claim we saw in the introduction – ROUGE doesn't correlate well with human judgments.
Finally, they mention "extensive research on modifying architectures and pre-training procedures for improving summarization."
This is acknowledging the broader context: there are many ways to improve summarization (better Transformer designs, better pre-training objectives, etc.). Their contribution is orthogonal – it's not about the architecture, but about the training objective.
| Concept | Explanation |
|---|---|
| Prior work baseline | Reference [73] did very similar work but with limitations (small models, online learning, low labeler agreement, resulting in extractive summaries) |
| Main novelties | Larger models, batch learning, better labeler consistency, algorithmic improvements (separate policy/value networks) |
| Generalizability | Human feedback as a training signal works across many NLP tasks, not just summarization |
| Theoretical roots | The reward modeling approach comes from learning-to-rank in information retrieval |
| Alternative approaches | Prior work optimized automatic metrics (ROUGE) with RL, but this paper argues learning from human feedback is superior |
By the end of this section, readers understand:
This sets up the paper to present their methods as a mature, well-motivated improvement rather than a radical departure.
Our approach is similar to the one outlined in [73], adapted to the batch setting. We start with an initial policy that ...
This section is the heart of the paper's methodological contribution. The authors are describing a three-step iterative process for training summarization models using human feedback rather than traditional supervised learning. Think of it as a "learn from humans, improve model, repeat" cycle.
Why does this matter? As mentioned in the introduction, training language models just to match human-written text (maximizing likelihood) doesn't align with what we actually care about—generating summaries that humans think are good. This section shows a practical way to close that gap.
The key insight: Instead of asking "Does this summary match reference text?" (supervised learning), they ask "Do humans prefer this summary?" (learning from preferences).
Let me break down what happens in each step:
What's happening:
Why pairs? This is clever: instead of asking "Rate this summary on a scale of 1-10" (which is hard and inconsistent), they ask "Which of these two is better?" (which is easier and more reliable). This is called pairwise comparison, and it generates relative preference signals rather than absolute ratings.
Mathematical intuition: For a given Reddit post , they create pairs where and are two candidate summaries. A human evaluator labels which one is preferred: where 1 means is better.
What's happening: This is where they translate human preferences into a mathematical function that can guide the policy.
The core idea: Train a supervised model (a neural network with parameters ) that learns to predict: "Given a post and summary , how likely is it that a human would prefer this summary?"
Mathematical formulation:
The reward model outputs a score: (a real number). For a pair of summaries from the same post , the model predicts the log odds that summary is better than .
The probability that humans prefer over is modeled as:
where is the sigmoid function: .
Why this form?
Training the reward model:
Given a dataset of human preference labels where indicates which summary humans preferred, they minimize the cross-entropy loss:
What each term means:
The reward model learns to assign higher scores to summaries humans prefer.
What's happening: Now they use the trained reward model as a "guide" to train the actual summarization model (called the "policy") to generate summaries that score highly according to the reward model.
The challenge: They can't just do supervised learning anymore—they need to optimize the reward model's output. This is a reinforcement learning (RL) problem where:
The algorithm: They use PPO (Proximal Policy Optimization), a popular RL algorithm. Without going into full RL theory, here's the intuition:
The update roughly increases proportionally to the reward:
What this means:
Here's the genius part: these three steps can repeat:
Each iteration, the reward model gets better at understanding human preferences, and the policy gets better at generating summaries humans prefer.
See Figure 2 in the section—it visualizes this cycle, showing how outputs from one step feed into the next.
Initial supervised learning: Before starting this loop, they first do a standard supervised fine-tuning step on the TL;DR dataset. This gets them a reasonable starting policy so they're not starting from a random model. This is common in RL: start with a good supervised baseline, then improve it.
Batch setting vs. Online: The text mentions they adapted this from prior work by moving to "batch setting." This means:
Practical note: The text admits they didn't follow this exact three-step procedure rigidly. In practice, they accumulated human labels over time and made algorithmic modifications (like separating policy and value networks, which is an RL optimization detail). But the conceptual framework is still these three steps.
By the end of this section, we understand the mechanism for how they'll improve summarization:
The rest of the paper will show empirically that this works better than traditional supervised learning, validate that the reward model generalizes to new domains (like news articles), and analyze what the model actually learned.
Datasets. We use the TL;DR summarization dataset, which contains ~3 million posts from reddit.com across a variety of to...
Before diving into the mathematical details of reward modeling and reinforcement learning (which come in later sections), the authors need to establish what problem they're actually solving and with what data. This section answers:
This is crucial because everything downstream—the reward model training and policy optimization—depends on having clear, well-defined training data and a precise objective. Think of this as establishing the "rules of the game" before building the game-playing engine.
The authors work primarily with the TL;DR dataset, which consists of:
However, they don't use all 3 million posts. They apply several filtering criteria:
The filtering process can be thought of as a sequence of constraints that narrows the dataset:
Whitelist filter: Keep only posts from subreddits that are "understandable to the general population"
Length constraint: Include only posts where human-written summaries have between 24 and 48 tokens
After filtering:
The authors explicitly state they "refer to this dataset simply as TL;DR" from this point forward—so whenever you see "TL;DR" in later sections, they mean this filtered version with 123,169 posts.
This is an important methodological choice. The authors could have used CNN/DM, a more standard benchmark in summarization research, but they explicitly chose TL;DR instead. Let's understand why:
CNN/DM is a news article summarization dataset. The authors observe three key problems:
Extractive baselines work too well: A simple "lead-3" baseline (just copy the first 3 sentences) outperforms the reference summaries according to their human evaluators
Supervised learning already cheats: A T5 model (a state-of-the-art transformer) fine-tuned with supervised learning on CNN/DM already surpasses reference summary quality
Poor task definition: Because simple copying works, it's hard to distinguish truly good summaries from mediocre ones
In contrast, with the Reddit TL;DR task:
Simple extractive baselines fail: Lead-3 copying doesn't work well because Reddit posts have different structure than news articles
There's improvement headroom: Supervised learning doesn't saturate performance
More faithful evaluation: Since humans must judge based on understanding rather than simple heuristics, the feedback is more meaningful
Key insight: The authors are deliberately choosing a harder, more interesting task where human feedback has the most value. This is a methodological decision about experimental design.
The authors define the task they're solving very explicitly:
"We define our ground-truth task as producing a model that generates summaries fewer than 48 tokens long that are as good as possible, according to our judgments."
Let's unpack this mathematically:
Where:
The authors operationalize "quality" specifically as:
"We judge summary quality by how faithfully the summary conveys the original post to a reader who can only read the summary and not the post."
This is a specific definition with mathematical implications:
Where fidelity means:
Crucially, the authors note they "rely on detailed procedures to ensure high agreement between labelers and us on the task."
This is critical because:
Noisy labels are problematic: If different humans disagree on what makes a good summary, the reward model will learn inconsistent patterns
Quantifying agreement: In practice, they measure inter-rater agreement using metrics like:
Where:
Why this matters for the rest of the paper: The reward model (Section 3.3) will be trained to predict these human preferences. If human preferences are noisy or inconsistent, the learned reward function will be noisy and the policy optimization will fail.
This section establishes the foundation for the entire approach:
| Element | What It Is | Why It Matters |
|---|---|---|
| Dataset | ~117k filtered Reddit posts with human summaries | Clean, well-defined source of training data |
| Task difficulty | Medium-hard: extractive baselines fail, but room for improvement | Ensures human feedback is meaningful and valuable |
| Quality definition | Faithfulness to source material | Gives concrete, actionable guidance to human labelers |
| Labeler agreement | High inter-rater reliability | Ensures consistent signal for training the reward model |
In the next sections (3.3 onwards), the authors will:
The quality of their results depends critically on the foundations laid here: clean data, consistent human judgments, and a well-defined objective.
Previous work on fine-tuning language models from human feedback reported 'a mismatch between the notion of quality we w...
This section addresses a critical problem in training language models with human feedback: getting humans to label data in a way that actually reflects what we care about. The authors discovered that previous work had a fundamental mismatch—the models learned to optimize what humans labeled as "good," but what humans labeled didn't always match what researchers actually thought was good.
Think of it like this: if you hire people to grade essays but don't train them properly or monitor their work, they might mark essays as "excellent" for reasons that don't align with what makes a truly excellent essay. The model then learns from these misaligned labels.
The authors' solution involves two key changes to how they collect human feedback, which results in much better agreement between what labelers think is good and what the researchers think is good.
From prior work (specifically reference [73]), there was a known issue:
"A mismatch between the notion of quality we wanted our model to learn, and what the humans labelers actually evaluated"
What this means mathematically:
Let's denote:
The problem was that in systematic ways. In other words, the labelers' judgments diverged from the researchers' standards.
This matters because in the framework described in Section 3.1, the reward model is trained to predict the human-labeled preferences. If those labels are misaligned with true quality, the reward model learns the wrong objective. Then when the policy is optimized against this reward model (Step 3 of Figure 2), it optimizes for the wrong thing.
What changed:
Previous work collected feedback in an online manner—meaning they continuously updated models and collected new comparisons in a real-time loop. The authors instead use an offline batch setting:
Why this helps:
The authors implement a hands-on process that involves:
The authors report inter-rater reliability metrics, which measure whether different raters (judges) agree with each other:
\text{Agreement} = \frac{\text{# of times labelers and researchers made same choice}}{\text{Total # of comparison tasks}}Specifically, they report:
What these numbers mean:
The and notation indicates confidence intervals—ranges of uncertainty around these estimates. Smaller confidence intervals (like the labelers') indicate more stable, reliable measurements.
Recall from Section 3.1, Step 2: the reward model is trained to predict human preferences. Formally, we can think of the reward model as learning to predict:
where is a Reddit post and is a candidate summary.
With high labeler-researcher agreement (77%), the human preference labels that the reward model trains on are reliable proxies for true quality. This means:
This directly addresses the mismatch problem from previous work.
| Aspect | Previous Work | This Paper |
|---|---|---|
| Collection Style | Online (continuous) | Offline (batches) |
| Labeler Management | Minimal oversight | Hands-on training & monitoring |
| Labeler-Researcher Agreement | Low (leading to stated mismatch) | High (77% ± 2%) |
| Result | Summaries good by labelers, poor by researchers | Summaries good by both labelers and researchers |
This section establishes the data quality foundation for the entire three-step process in Section 3.1:
Without this careful attention to human feedback quality, the entire pipeline would suffer from the mismatch problem documented in prior work.
All of our models are Transformer decoders in the style of GPT-3. We conduct our human feedback experiments on models wi...
Before diving into the technical details of training and evaluation, the authors need to establish what models they're working with. This section describes the foundational architecture and baseline approaches that everything else builds upon. Think of it as laying out the "players" in the game before explaining the rules:
This is crucial because the paper's main contribution—learning from human feedback—only matters if we can compare it fairly against strong baselines.
The authors use Transformer decoders in the style of GPT-3. Let me unpack this:
Mathematically, if we have a sequence of tokens , the model learns to compute:
where represents all the model parameters. The model generates text by repeatedly sampling the next token from this conditional probability distribution.
The authors test two sizes:
Why two sizes? To see if the approach scales and whether larger models benefit more from human feedback than smaller ones.
The models begin with pretraining on a large text corpus. This is like teaching the model to understand language generally before teaching it the specific task of summarization.
What does pretraining accomplish?
The model learns to minimize the language modeling loss:
Breaking this down:
By solving this, the model learns useful patterns about language structure, grammar, facts, and reasoning.
The authors also evaluate their pretrained models directly by using a technique called "in-context learning" or "few-shot prompting":
How it works: Rather than fine-tuning on the task, they pad the context with examples of high-quality summaries from the dataset and ask the model to continue the pattern.
Example structure:
[Reddit post 1]
Summary: [high-quality reference summary 1]
[Reddit post 2]
Summary: [high-quality reference summary 2]
[New Reddit post to summarize]
Summary: [model generates this]
This tests whether the pretrained model can "learn" the task just from seeing examples, without any gradient-based fine-tuning. The results establish a lower bound on performance—any method should beat this if it's actually improving.
This is the standard approach to training summarization models. It serves multiple purposes:
The supervised models are fine-tuned using standard cross-entropy loss:
Let me break down each component:
| Component | Meaning |
|---|---|
| Number of training examples (posts) in the filtered TL;DR dataset | |
| The -th token of the reference summary for post | |
| The length (number of tokens) of post 's reference summary | |
| The -th Reddit post | |
| The model's parameters being optimized |
Intuition: For each post-summary pair, the model learns to predict each token of the reference summary given the post and all previously generated tokens. This is classic teacher-forcing: we're teaching the model to mimic human-written summaries.
Temperature and Sampling Strategy:
When generating summaries, the authors use , which means greedy decoding (always picking the most likely next token).
Why instead of higher temperatures?
They found worked better than higher temperatures or nucleus sampling (which selects from the top- most likely tokens). This is somewhat surprising but suggests that for summarization, consistency matters more than diversity.
To validate that their supervised models are strong, they:
ROUGE (Recall-Oriented Understudy for Gisting Evaluation) measures the overlap between generated and reference summaries:
where is the n-gram size (typically 1, 2, or L for longest common subsequence).
Why does this validation matter? It proves their supervised baseline is competitive with published methods, so any improvements from human feedback are meaningful—not just improvements over a weak baseline.
| Model Type | Source | Purpose |
|---|---|---|
| Pretrained | Language modeling on large corpus | Zero-shot baseline (lower bound) |
| Supervised | Fine-tuned on TL;DR reference summaries | Initial policy, reward model initialization, strong baseline |
| Human feedback | Further fine-tuned via RL using reward model | Main contribution (discussed in later sections) |
The flow is: Pretrained → Supervised → RL-trained (which we'll see in the next section).
This section establishes strong baselines. The authors will later show that by incorporating human feedback (Sections 3.5 and beyond), they can beat these supervised models—but only because the supervised models themselves are already competitive with published work. This makes the human feedback improvements credible rather than trivial.
Reward models. To train our reward models, we start from a supervised baseline, as described above, then add a randomly ...
This section describes the crucial machinery that makes the entire paper work. The authors have three goals here:
Think of it like teaching an AI judge (the reward model) to rate summaries, then using that judge's feedback to train a better summarizer (the policy).
The reward model starts from a supervised model (trained to copy reference summaries) and adds a simple linear layer on top. This layer outputs a single scalar number representing "how good is this summary?"
The key insight: We don't need the model to predict absolute quality—just to rank which of two summaries is better. This is called pairwise comparison and is much more stable than predicting absolute scores.
Let me break down each component:
Variables and their meanings:
What does this loss mean mathematically?
We want to train the model so that (the preferred summary gets a higher score). The key quantity is the difference:
We pass this difference through the sigmoid function and take the log:
This is the log-likelihood from binary cross-entropy, a standard classification loss. Here's why it works:
Intuition: Think of this as teaching the model "if humans preferred summary A over B, make sure you rate A higher than B."
After training, the authors normalize reward outputs so that the reference summaries (human-written TL;DRs) have a mean score of 0. This is a calibration step—it ensures the reward model has a meaningful baseline. Summaries better than the references will have positive scores; worse ones will be negative.
You might ask: "Can't we just ask the reward model for a summary directly?"
No—and this is crucial. The reward model learned to judge summaries it saw during training, but if we optimize it too aggressively, the policy will find adversarial examples: summaries that score high on the reward model but are actually terrible in ways the humans never explicitly trained against.
This is called reward hacking or distributional shift: the policy generates summaries that are out-of-distribution relative to what the reward model has seen.
We use Proximal Policy Optimization (PPO), a reinforcement learning algorithm, but with a crucial modification: we penalize the KL divergence from the original supervised model.
The full reward function is:
Breaking this down:
Part 1: The reward term
Part 2: The KL penalty
This is a bit mathematically dense, so let's unpack it carefully:
What is KL divergence?
KL divergence measures how different two probability distributions are. For two distributions and :
What do the two policies represent?
What does the KL term do?
The term measures, for each summary , how much more likely the RL policy is compared to the SFT policy:
The parameter controls the strength of this penalty. High means "don't drift far from the supervised model"; low means "aggressively optimize the reward."
The full reward equation gives us the optimization target:
During RL training, we use PPO to maximize this reward, which naturally balances two competing goals.
The authors explicitly state the KL term serves two purposes:
Entropy bonus (exploration): The KL term encourages the policy to spread probability mass across multiple summaries rather than concentrating on one. This prevents the policy from getting stuck in a bad local optimum.
Distributional safety: It prevents the policy from learning to exploit the reward model with out-of-distribution summaries that the reward model never learned about.
For PPO to work, we also need a value function—a separate model that predicts the expected long-term reward from a given state.
Key design choice: The authors use completely separate parameters for the value function, not the policy parameters.
Why does this matter? If the value function were part of the policy, gradient updates to the value function could inadvertently scramble the pre-trained knowledge in the policy early in training. By keeping them separate, they preserve the starting supervised model's knowledge while learning a good value estimate.
Initialization: The value function is initialized from the reward model parameters. This makes intuitive sense: initially, the best estimate of "how much reward will I get from this state?" is just what the reward model thinks. As RL training progresses, the value function learns its own better estimates.
| Component | Purpose | Key Equation |
|---|---|---|
| Reward Model | Learn to predict human preferences | |
| RL Policy | Generate high-reward summaries while staying close to supervised baseline | |
| Value Function | Estimate future reward (separate parameters) | Initialized from reward model, learned via PPO |
This section implements a complete pipeline:
The result is a summarization model that optimizes for human preferences rather than ROUGE scores—which is precisely what the paper's title promises.
Perfect! The plot shows both the loss and gradient. The asymmetry is key:
The paper uses this loss within a specific pipeline:
The equation in the paper:
uses the trained reward model as a scoring function. The loss we analyzed is how you train that reward model.
1. Binary cross-entropy form
This is exactly binary cross-entropy: "how surprised are we that the preferred summary scored higher?"
2. Symmetry under sign flip If we swap which summary is preferred, the loss changes from to . But their average behavior is symmetric: both push the model to make clear distinctions.
3. Margin-like behavior The loss only cares about the difference in rewards, not their absolute values. A margin of 1 unit produces the same loss whether the scores are or .
4. Stability Because the gradient is bounded (between -1 and 0), this loss doesn't suffer from vanishing or exploding gradients — a major practical advantage.
This loss function teaches a reward model to rank summaries by human preference. It:
This trained reward model then becomes the objective function for reinforcement learning that optimizes the policy to generate better summaries.
Understanding what -log(sigmoid(z)) simplifies to




Simplifying the log of the sigmoid function




Visualizing the loss as a function of reward difference



Loss when z = -1 (non-preferred summary is 1 unit higher)




Loss when z = 3 (preferred summary is 3 units higher)




Finding the gradient for backpropagation




Comparing loss and gradient to see learning dynamics




Perfect! This tells us that .
So the derivative of the KL penalty with respect to the policy is:
This means:
This equation orchestrates a delicate balance:
The reward model term pushes the policy to generate summaries humans prefer
The KL penalty term restrains the policy from diverging too far from the supervised baseline by:
The hyperparameter controls this trade-off:
This formulation is elegant because it avoids the need for explicit trust region constraints (like in natural policy gradient methods) while achieving similar protective effects through the principled information-theoretic KL divergence penalty.
Simplifying the log-ratio in the KL divergence term




Visualizing a simple reward function with competing objectives: reward maximization vs KL penalty



Computing a concrete example of the reward function with specific numerical values




Showing how the KL weight parameter beta affects the total reward for different policy updates

Visualizing how different beta values change the reward landscape as policy drifts from baseline (x = prob ratio)



Exploring the relationship between the log-ratio and information-theoretic quantities


Finding the derivative of the log term to understand how the policy responds to incentives




Policies trained with human feedback are preferred to much larger supervised policies. Our main results evaluating our h...
This section is the payoff of the entire paper. After spending several sections building the theoretical and methodological foundation (collecting human feedback, training reward models, using RL to optimize summaries), we now see the empirical results: Do models trained to optimize human preferences actually produce better summaries than traditional supervised learning approaches?
The answer is a resounding yes, and this section provides both quantitative evidence and qualitative analysis to demonstrate why and how much better these models perform.
The headline result is striking: A 1.3B parameter model trained with human feedback (PPO) beats a 10× larger supervised model (13B parameters). This is significant because it shows that optimizing the "right objective" (human preferences) can be more valuable than simply making models larger.
The metric is intuitive but rigorous:
This is a win rate or head-to-head comparison metric. Instead of using ROUGE or BLEU scores (which the paper argues are poor proxies for quality), they directly compare:
The fact that the 1.3B PPO model beats a 13B supervised model is the key insight here — it's not just about model scale, it's about what objective you optimize for.
There's a potential statistical confound here: What if the PPO models are only better because they generate longer summaries?
This is a legitimate concern because:
They perform a controlled analysis where they compare summaries of similar lengths. Formally, this means:
The mathematical intuition: By restricting the comparison set to pairs of summaries where (using to denote length), they isolate the quality differences from length differences.
This is important because it shows the improvements aren't just an artifact of length — the models are genuinely generating better content, not just more content.
Rather than a single "quality" score, they ask human labelers to evaluate summaries across four independent dimensions (or "axes"):
Each dimension is rated on a 7-point Likert scale (1 = poor, 7 = excellent), which gives fine-grained feedback.
For each dimension , they can compute:
where is the score (1-7) that labeler gave on dimension .
They do this for three summary types:
The data indicates a consistent and substantial improvement across all dimensions:
| Summary Type | Coverage | Accuracy | Coherence | Overall Quality |
|---|---|---|---|---|
| 6.7B PPO | ↑↑ | ↑ | ↑ | ↑↑↑ |
| 6.7B Supervised | Baseline | Baseline | Baseline | Baseline |
| Reference | Lower | Lower | Lower | Lower |
Particularly notable: Coverage shows the largest improvement. This makes sense because the PPO model is explicitly optimizing to match human preferences, and coverage (how much relevant information is included) is a major component of what humans care about when evaluating summaries.
The paper highlights one specific finding:
This is the probability of achieving a perfect 7/7 score given which model generated the summary:
This is striking because it shows the PPO model doesn't just beat the baselines on average — it actually produces more consistently excellent summaries. The distribution shifts toward the high end.
Recall from the previous section that the reward model is trained with the loss:
The reason the PPO models perform so well is that they optimize:
The reward model is directly trained to predict what humans prefer. By using RL to maximize this reward, the policy learns to produce summaries that align with human judgments across all the dimensions they care about — coverage, accuracy, and coherence.
Human preferences are a better training objective than ROUGE/BLEU — The PPO model beats supervised baselines substantially.
Scale is less important than the right objective — A smaller model optimized for the right thing beats a much larger supervised model.
Length isn't the confound — Even controlling for length, PPO models are preferred ~56% of the time.
Improvements are multidimensional — Better coverage, accuracy, and coherence all contribute, with coverage being the primary driver.
Consistency matters — The PPO model doesn't just beat baselines on average; it produces more consistently high-quality outputs (45% perfect scores vs. 20-23%).
Our human feedback models can also generate excellent summaries of CNN/DM news articles without any further training (Fi...
This section answers a critical question: Does a model trained to optimize human preferences on one dataset (Reddit TL;DR) actually learn generalizable principles of good summarization, or does it just overfit to Reddit's specific characteristics?
The answer is crucial because it determines whether the human feedback approach from Section 4.1 is a broadly applicable method or merely a domain-specific trick. If the model transfers well to completely different data (CNN/DM news articles), that's strong evidence the reward model learned something fundamental about what makes summaries good.
The authors show that their 6.7B parameter human feedback model, despite being trained exclusively on Reddit posts, produces CNN/DM news summaries that are:
This is remarkable because there's zero overlap in the training data domains.
Let's think about what the reward model learned during training on Reddit:
The Reward Model's Training (from Section 3.4):
What the Reward Model Captures: Rather than learning "what Reddit summaries look like," the model learns abstract quality principles:
These principles are domain-agnostic—they apply equally well to news articles as to Reddit posts.
Why the RL Policy Benefits: The RL policy (trained via PPO using this reward signal) learns to produce summaries that score highly according to these general principles. Since the principles generalize, so does the policy.
The figure plots human quality ratings (on a 7-point Likert scale) for different models on CNN/DM:
Models compared:
The key insight: The TL;DR human feedback models track the CNN/DM supervised baseline closely, despite never seeing CNN/DM data during training.
This is where we need to be careful about confounding variables.
The Problem: The human feedback models generate much shorter summaries than CNN/DM supervised models. Shorter summaries might naturally receive lower quality ratings—they provide less information. This confounds the comparison: Are they performing worse, or just choosing a different length?
The Solution: Figure 4(b) shows the relationship between average quality scores and average summary length:
By plotting quality as a function of length, we can see: if we controlled for length (made all models generate the same-length summaries), would the human feedback model be better or worse?
The Finding: The authors observe that the human feedback model likely sits on a curve where it would score higher if generating longer summaries. This suggests:
Here's where the math and methodology matter:
The authors acknowledge a statistical confound: summary length is correlated with perceived quality. If we let denote summary length (measured in tokens), we have:
where:
During RL training on TL;DR, the reward model may have learned a particular optimal length distribution that was appropriate for Reddit. When deployed on CNN/DM (which may have different optimal lengths), this creates a systematic bias.
Interpreting the bias: The ~5% difference they mention in Section 4.1 is a sensitivity analysis—when they statistically adjust for length differences, the human preference gap shrinks slightly. This is a sign of honest methodological rigor.
The evaluation uses a more nuanced metric than just "overall quality." For each summary, human raters score:
This breakdown is valuable because it lets us diagnose where models succeed or fail. A model might have high coherence but poor coverage, for instance.
Formally, let's denote:
The transfer works if:
where is a model trained on CNN/DM directly.
This approximation is not guaranteed because:
That it does hold is empirical evidence that the reward model learned transferable features about summarization quality.
Generalization: The reward model generalizes beyond its training distribution—a key validation of the approach
Cost-effectiveness: You don't need to collect human feedback for every domain. One well-trained reward model can guide policy learning across multiple domains
Scalability: This suggests the human feedback approach could be a foundation for multi-domain summarization systems
| Aspect | Finding |
|---|---|
| Transfer capability | Human feedback models trained on Reddit generalize to CNN/DM |
| Relative performance | 6.7B human feedback ≈ 6.7B CNN/DM supervised (with shorter summaries) |
| Quality dimensions | Consistent improvements across coverage, accuracy, coherence |
| Confounding factor | Length differences account for ~5% of the gap |
| Interpretation | Reward model learned domain-general principles of quality |
What happens as we optimize the reward model? Optimizing against our reward model is supposed to make our policy align w...
This section addresses a critical practical problem: How well does the reward model actually work as a proxy for human judgment?
In the earlier sections, the paper described building a reward model to predict which summaries humans prefer. But a reward model is just an approximation—it's trained on limited data and has finite capacity. The authors want to understand:
This is important because the entire pipeline (RL training the policy against the reward signal) depends on the reward model being a good judge of summary quality. If the reward model is flawed, the policy will learn to optimize for the wrong things.
When you have an imperfect reward model and you optimize against it aggressively, you can encounter reward hacking: the policy learns to game the reward model in ways that don't actually improve real human-judged quality.
The authors create multiple policies trained with different KL penalty coefficients (), where controls how much the policy is allowed to deviate from the original supervised baseline.
Recall from the previous section that the reward used in RL training is:
Here's what each term means:
When is large, the penalty is strong, so the policy stays close to the original supervised model. When is small, the policy is free to diverge more and optimize harder for the reward.
[Figure 5: Preference scores versus degree of reward model optimization]
The figure plots two curves against increasing optimization strength:
This demonstrates overfitting to a learned reward function:
The reward model, being a finite neural network trained on limited data, has blind spots. When you optimize too hard against it, the policy discovers these blind spots and exploits them. The policy generates adversarial examples—summaries that score high on the reward model but aren't actually good.
Analogy: Imagine grading papers with a flawed rubric. If students optimize only for the rubric without caring about actual learning, they'll eventually game it in ways the rubric doesn't account for.
The authors note this also happens with ROUGE (the traditional metric for summarization), which suggests this is a fundamental challenge with any learned or heuristic reward function, not unique to their approach.
Now that we know overfitting is possible, the authors ask: What factors improve the reward model's basic quality? Specifically, how do two factors affect performance?
The authors train 7 reward models with varying sizes and training data amounts:
For each combination, they measure validation set accuracy: On held-out human comparisons the model hasn't seen, does the reward model correctly predict which summary humans prefer?
[Figure 6: Reward model performance versus data size and model size]
Two clear scaling laws emerge:
Interpretation: Model capacity matters more than training data quantity for this task. This makes sense: with a fixed budget to improve the reward model, you get more benefit from a bigger network than from more comparisons. However, this doesn't mean data is unimportant—it means they're operating in a regime where the model architecture is the bottleneck.
The authors probe the reward model's behavior on several validation sets to understand its strengths and limitations. Let's go through each finding:
The authors test whether the reward model trained on Reddit TL;DR summaries transfers to CNN/DM news articles (a different dataset, different writing style, different domain).
Results:
What this means: The larger model nearly matches human consistency! This is a strong sign the reward model has learned something general about summary quality, not just dataset-specific artifacts.
The authors create a special validation set by having humans make minimal edits to summaries to improve them. They ask: Does the reward model prefer the improved version?
Results:
What this means: The reward model is sensitive to small semantic improvements, showing it's not just pattern-matching surface features.
The authors test whether the reward model is fooled by simple manipulations. They take pairs of (reference summary, other summary) and flip which is presented as "original" vs. "comparison."
Results:
What this means: The model isn't easily fooled by presentation order. It's actually evaluating the content, not gaming trivial features.
However, the reward model has one clear failure mode: it's biased toward longer summaries.
The authors compare:
What this means: When an edit makes a summary shorter, the reward model only agrees with humans 62.6% of the time. This is the key discovered weakness—the model has learned to associate summary length with quality, which isn't always valid.
During RL training, the policy is optimizing against . If the reward model systematically overvalues length, the policy will learn to generate longer summaries than optimal. This connects back to Section 4.1, where the authors had to explicitly control for length when comparing to baselines—the policies were generating longer summaries.
| Aspect | Finding |
|---|---|
| Overfitting risk | Aggressive optimization beats the reward, causing alignment failure |
| Scaling laws | Model size helps more than data size; both improve reward accuracy |
| Generalization | Reward model transfers well to new domains (nearly human-level on CNN/DM) |
| Sensitivity | Detects meaningful semantic edits (82.8% agreement with humans) |
| Robustness | Resistant to trivial manipulations (97.2% on role reversals) |
| Weakness | Biased toward longer summaries (only 62.6% accuracy on shortening edits) |
This analysis is honest and important: it shows the reward model is good but not perfect. The approach works because:
But it also reveals we should be careful about pushing optimization too hard, and we should be aware of subtle biases (like length preference) that can leak into downstream model behavior.
Evaluation. We study how well various automatic metrics act as predictors for human preferences, and compare them to our...
Here's the core question: How good are the metrics we use to evaluate summaries?
Throughout machine learning, we rely on automatic metrics to judge model quality. In summarization, the most common metric is ROUGE (a family of metrics based on n-gram overlap with reference summaries). The paper's central argument is that these standard metrics might not actually measure what humans care about.
This section tests that claim empirically. The researchers ask:
This matters because if we train models to optimize a bad metric, we'll get worse results, even though the metric number goes up. This is the core lesson the paper wants to convey.
The authors measure how well different automatic metrics predict human preferences. Think of this as a correlation problem: for any two summaries, does the metric rank them the same way humans do?
The metrics being compared:
What is "agreement" or "accuracy"?
When comparing two summaries and , we ask: does the metric rank them the same way humans do? If humans prefer and the metric gives it a higher score, that's agreement. Agreement rate is simply:
\text{Agreement} = \frac{\text{# pairs where metric and humans agree}}{\text{Total # pairs compared}}This is expressed as a percentage. 50% agreement means the metric is no better than a coin flip.
The authors show that reward models consistently outperform ROUGE, especially on the CNN/DM transfer task (where the RM was never trained).
Specifically:
This is the critical insight. ROUGE doesn't correlate with actual improvements:
In other words, when the paper's models get genuinely better (according to humans), ROUGE gets worse at predicting quality. This is exactly backwards from what we want.
Why does this happen?
Recall from Section 4.1 that human feedback models learned to generate longer summaries. The human feedback models also have different stylistic properties—they might be more abstractive, for instance. ROUGE is fundamentally based on n-gram overlap with reference summaries, so:
\text{ROUGE-L} \propto \frac{\text{# overlapping n-grams with reference}}{\text{total n-grams}}When a model learns a different way of expressing ideas (optimizing for human preferences rather than copying), ROUGE penalizes it even though humans prefer it. The metric is misaligned with the actual goal.
Similarly, log probability agreement drops to ≤50% on human feedback model comparisons. The supervised model's own confidence in what makes a good summary becomes uncorrelated with actual human preferences.
Figure 7 shows what happens when we iteratively improve summaries by optimizing different metrics. This uses best-of-N rejection sampling, a simple technique:
The -axis shows "amount of optimization" (how many candidates we sample). More samples = more optimization effort = ability to find better summaries according to the metric.
The key observation:
For ROUGE optimization:
For RM optimization:
When we optimize ROUGE, we're maximizing:
This encourages:
But humans prefer:
These objectives can be opposite — a summary that deviates from reference text might actually communicate better.
The RM, trained on human comparisons, directly optimizes what we actually care about. As noted in Section 4.3, optimizing the RM initially improves summaries, though it can eventually overfit (Figure 5).
Section 4.3 showed that optimizing against the RM too hard eventually hurts (Figure 5 — over-optimization causes overfitting). Section 4.4 shows that even with this limitation, the RM is still better than the alternative (optimizing ROUGE), which has its own overfitting problem but worse overall performance.
Section 4.1 showed that human feedback models significantly outperform supervised models. Section 4.4 explains why: they were trained with a signal (human preferences) that actual automatic metrics don't capture well. This is the payoff for the complexity of collecting human feedback data.
| Metric | In-Distribution | Out-of-Distribution | Optimization Performance |
|---|---|---|---|
| ROUGE | 57% agreement | Falls to ~50% | Peaks early, low quality |
| Log probability | Decent initially | ≤50% on HF models | Poor alignment |
| Reward model | High agreement | 62-66.5% (near inter-labeler) | Sustains improvement |
The core lesson: Just because a metric is easy to compute doesn't mean it measures what you care about. When building ML systems, the metric you optimize should be validated against what humans actually prefer. Otherwise, you're optimizing the wrong thing.
This is why the paper advocates for learning reward models from human feedback — it's a more principled way to align our training objective with our actual goal.
Limitations. One limitation of our work is the time and cost required to produce our final models. Notably, fine-tuning ...
The Discussion section wraps up the paper by acknowledging what the authors have achieved, what they haven't achieved, and what remains to be done. Think of it as: "Here's what we did well, here's where we're limited, here's what we could do next, and here's what people should be careful about."
The section covers four main themes:
Let me walk through each subsection carefully.
The authors are being honest about a fundamental tradeoff:
"Fine-tuning our 6.7B model with RL required approximately 320 GPU-days."
What does this mean? Let's break it down:
The authors also point out:
"The training set took thousands of labeler hours and required significant researcher time to ensure quality."
Why this matters mathematically:
If we think about the cost function for building an ML system:
Their approach is:
The comparison problem they mention:
"For this reason, we were unable to collect baselines such as an equivalent amount of high-quality human demonstrations for supervised baselines."
What they're saying: A fair comparison would require training a supervised model on the same amount of human effort. If they spent X human hours on comparison data, they should have collected X hours of high-quality demonstrations for a supervised baseline. But they didn't have the budget to do this.
This is important because it means we can't definitively say: "Human feedback RL is better than supervised learning with similar human effort." We can only say: "Human feedback RL produces better summaries, and here's how much it cost us."
They hint at the answer:
"We believe reward modeling is more likely to scale to tasks where it is extremely skill-intensive or time-consuming to provide good demonstrations."
The intuition:
Compare two scenarios:
Scenario A (Summarization):
Scenario B (An easier task, like labeling whether an image contains a cat):
So the math isn't just about computational cost—it's about human effort efficiency:
\text{Effort} = \text{(Skill required for demo)} \times \text{(# of demos needed)} \text{ vs. } \text{(Effort per comparison)} \times \text{(# of comparisons needed)}For summarization, the first term is high, so comparisons win. For easier tasks, direct demonstration might win.
The authors state:
"The methods in this paper could be applied to any task where humans can compare samples, including dialogue, machine translation, question answering, speech synthesis, and music generation."
What this means mathematically:
The core algorithm doesn't depend on summarization specifically. Let's denote:
Their method works for any where:
This is very general! It applies to:
The core workflow is always:
"We expect this method to be particularly important for generating long samples, where the distributional shift and degeneracy of maximum likelihood samples can be problematic."
What does "distributional shift" and "degeneracy of maximum likelihood" mean?
In supervised learning, models learn to predict reference summaries using maximum likelihood loss:
For long sequences, two problems arise:
Problem 1 - Distributional Shift:
Problem 2 - Degeneracy of Maximum Likelihood:
Why human feedback helps: The reward model can identify "genuinely good" long outputs that the ML objective would ignore.
"It may be possible to improve sample efficiency by training to predict feedback across many tasks."
The mathematical idea:
Instead of training separate reward models for each task:
You could train a single reward model on feedback from multiple tasks:
This is a transfer learning scenario. The intuition is that the reward model learns general principles of quality (fluency, coherence, relevance) that apply across tasks, reducing the amount of task-specific data needed.
"We are particularly interested in scaling human feedback to tasks where humans can't easily evaluate the quality of model outputs."
This is the hardest case. Examples:
The proposed solution:
"One approach is to train ML systems to help humans perform the evaluation task quickly and accurately."
What this means:
You need a two-stage process:
This is recursive ML—using ML to enable human feedback, which trains more ML. Mathematically:
"There is also a rich landscape of human feedback methods beyond binary comparisons that could be explored."
Currently, they use binary comparisons: "Prefer summary A or summary B?" But humans could provide richer feedback:
| Feedback Type | Mathematical Form | Cost | Information |
|---|---|---|---|
| Binary comparison | Low | Low | |
| Ranking | Medium | Medium | |
| Edits | Original , edited | Medium-High | High |
| Explanations | Text explaining preference | High | Very High |
| Ratings | Low-Medium | Medium |
Key insight from the paper (Section 4.3): They show that reward models can distinguish summaries with small but important changes (79.4%-82.8% accuracy on edited summaries). This suggests that richer feedback signals (like edits) could train even better reward models.
The mathematical potential:
If you have edit pairs where the edit improves the summary, you gain more information than from a binary comparison:
The edit information could help the reward model understand why one summary is better, not just that it's better.
This subsection is crucial and often overlooked. Let's break down the key tensions:
"Our research is primarily motivated by the potential positive effects of aligning machine learning algorithms with the designer's preferences. In the long term... it will likely become increasingly difficult to ensure that they are behaving safely. Unfortunately, our techniques also enable malicious actors to more easily train models that cause societal harm."
What this means:
The same method that helps align AI with good intentions can be weaponized:
| Use Case | Intent | Process | Outcome |
|---|---|---|---|
| Positive | Create helpful summaries | Collect human feedback on helpful summaries → Train reward model → Optimize for helpfulness | System aligns with human values |
| Negative | Spread misinformation | Collect human feedback on persuasive misinformation → Train reward model → Optimize for persuasiveness | System aligns with misuse |
Mathematically, both use the same objective:
The difference is what is trained to recognize. If learned to recognize "helpful, accurate summaries," you get the first outcome. If learned to recognize "persuasive misinformation," you get the second.
"Since the dataset consists of user-submitted posts with minimal moderation, they often contain content that is offensive or reflects harmful social biases."
The problem:
When training on real-world user data, the human preferences reflect the full spectrum of human values—including biases and harmful preferences.
Imagine their dataset includes comparisons where humans prefer summaries that:
When the model trains on these preferences:
The resulting model becomes:
This optimal policy may produce summaries that amplify harmful biases, not because anyone intended it, but because the reward model learned to predict biased preferences.
"We recommend that the potential harms of our models be thoroughly studied before deploying them in user-facing applications."
What this means in practice:
Before deployment, you'd want:
| Aspect | Core Message |
|---|---|
| Limitations | High computational cost (320 GPU-days) + high human cost (thousands of labeler hours). Worth it when demonstrations would be harder than comparisons. |
| Future Directions | Generalizes to any task with human comparisons. Particularly powerful for long sequences. Could work across multiple tasks. Could help humans evaluate things that are normally hard to evaluate. |
| Technical Extensions | Move beyond binary comparisons to richer feedback (edits, explanations, rankings). |
| Broader Impacts | Same technique enables both aligned AI and misuse. Real-world data reflects human biases. Need careful deployment and auditing. |
The section essentially says: "Here's what we built and why it matters. Here are the costs. Here's where the field should go next. And here's why you should be careful with this power."
Here, we discuss the pre-processing steps that we apply to the TL;DR dataset. We first remove all duplicate posts by che...
Before we can train any machine learning model, we need high-quality data. This section describes the crucial data preprocessing and cleaning pipeline used to prepare the TL;DR dataset for training. This is important because:
Think of this section as the "data hygiene" step—essential but unglamorous work that makes everything downstream work better.
The authors apply a sequential filtering pipeline to the raw TL;DR dataset. Let's think of this mathematically:
Let denote the raw, unfiltered dataset. The authors apply a series of filters in sequence:
where each filter is a function that removes certain posts and/or summaries based on specific criteria. Let's break down each filter:
What it does: Identify posts with identical text bodies.
Mathematical formulation: For each pair of posts where , if the text body (exact string equality), keep only one copy.
Empirical result: ~20,000 exact duplicates removed.
Why this matters: Duplicates would artificially inflate agreement patterns in the training data and bias the reward model.
What it does: Carefully extract TL;DR summaries using heuristics, and keep only top-level posts (not comments/replies).
Why this matters:
What it does: Remove posts from subreddits not on a pre-approved list.
Why this matters: Keeps the dataset focused on relevant subreddits and filters out potentially problematic content early.
What it does: Exclude posts whose titles start with variants of "Edit," "Update," or similar meta-commentary.
Why this matters: These are often follow-ups or corrections, not complete narratives—they may not be suitable for standalone summarization.
What it does: Remove posts containing certain sensitive topics (graphic sex, suicide, etc.) using keyword/heuristic detection.
Why this matters: Addresses ethical concerns about harmful content being included in training data.
What it does: Remove any post whose body exceeds 512 tokens.
Mathematical formulation: Keep post if and only if:
where denotes the cardinality (length) of a sequence.
Why this matters: The language models used have fixed context windows (maximum sequence length). Posts longer than this cannot fit in the model's input, so including them would be wasteful.
Result after body filtering: 287,790 posts
The authors reserve approximately 5% of these 287,790 posts as a validation set:
After filtering the posts themselves, the authors apply additional filtering to the reference summaries (the human-written TL;DR's) used for training supervised baselines.
Remove summaries starting with "Edit," "Update," "P.S.," etc.
Heuristically remove summaries with certain profanity levels.
Why: Aligns with content moderation concerns for deployment.
Keep summary if:
where again denotes token count.
Why this matters:
Final result: 123,169 posts with high-quality summaries, again with ~5% held out as validation.
The authors note that approximately 2/3 of the TL;DR dataset consists of relationship/relationship-advice posts. This is a significant composition bias:
Why this is a concern:
Why the authors aren't too worried:
Let's summarize what remains after all filtering:
| Stage | Number of Posts | Notes |
|---|---|---|
| Raw dataset | Unknown (not stated) | Starting point |
| After post-level filtering | 287,790 | Final before summary filtering |
| After summary-level filtering | 123,169 | Final, usable dataset |
| Training set (~95%) | ~116,980 | Used for training |
| Validation set (~5%) | ~6,189 | Used for evaluation during training |
The 57% reduction (from 287,790 → 123,169) shows that summary-level filtering was the most aggressive step. This makes sense: the summary filtering ensures that only high-quality, well-formed summaries are used for training supervised baselines.
By explicitly documenting all these filtering steps, the authors enable:
This level of documentation is a best practice often overlooked in ML papers, but it's crucial for scientific integrity.
B.1 Hyperparameters. All models follow the standard Transformer architecture, with 2048 learned position embeddings. All...
This section is essentially a recipe book for how the authors actually trained all their models. While the main paper describes the conceptual approach (supervised learning → reward modeling → reinforcement learning), this appendix provides the specific numerical knobs they turned to make it work.
Why does this matter? Because machine learning is surprisingly sensitive to these details. Two models with identical architecture can perform vastly differently based on learning rates, batch sizes, and training schedules. By documenting these choices, the authors enable:
All models use a Transformer architecture with 2048 learned position embeddings. Let me unpack what this means:
Transformer: The standard neural network architecture (like GPT, BERT) that uses attention mechanisms. You don't need to understand attention in detail, but think of it as a mechanism that lets the model focus on relevant parts of the input.
Learned position embeddings: These are trainable vectors of dimension (the model's hidden dimension) that encode where a token appears in the sequence. There are 2048 of them (one for each position up to a maximum sequence length of 2048 tokens). During training, the model learns what these position embeddings should be, rather than using a fixed mathematical formula.
The authors train with:
The notation here uses standard optimization terminology:
Models start from a pretrained checkpoint trained on massive text:
Training corpus: Commoncrawl, Webtext, books, and Wikipedia
Total tokens seen: billion tokens
Schedule: 1-3 epochs over this data (epoch = one complete pass through the dataset)
Learning rate schedule: Cosine annealing with warmup:
Where:
Batch size: 2048 tokens per example, with batch size ramped up gradually during pretraining (starting small, increasing over time)
This pretraining is the foundation—all downstream models (supervised, reward models, RL policies) start from this pretrained checkpoint and fine-tune on task-specific data.
Once pretrained, models are fine-tuned on summarization data:
Learning rate selection: The authors do a hyperparameter sweep, testing at least 7 different learning rates on a log-linear scale. The results were:
| Model Size | Dataset | Learning Rate |
|---|---|---|
| 1.3B | TL;DR | |
| 3B | TL;DR | |
| 6.7B | TL;DR | |
| 13B | TL;DR | |
| 6.7B | CNN/DM |
Key observation: Larger models use smaller learning rates. This is standard practice—bigger models with more parameters need more careful, conservative updates or they become unstable.
Training schedule:
Why only 1 epoch? Because the models already have strong priors from pretraining. Fine-tuning for too many epochs would cause catastrophic forgetting—the model would overfit to summarization and lose its general knowledge.
This is where things diverge. The reward model is trained differently:
Initialization: Start from the supervised baseline, but add a reward head—a small neural network on top that outputs a scalar reward value instead of token probabilities.
Reward head initialization: The weights of the reward head are initialized from a normal distribution:
Where:
Training hyperparameters:
Why these differences from supervised learning?
This is where the policy is optimized using RL. PPO = Proximal Policy Optimization, an RL algorithm that updates a policy by making it better while not straying too far from the original.
Setup:
Key RL parameters:
This is the Generalized Advantage Estimate (GAE) formula, where:
Learning rate schedule: Linear decay from initial value to 0
KL coefficient:
This controls a penalty term in the RL loss. The full objective becomes:
Where:
This is crucial: without the KL penalty, the policy might optimize the reward model so aggressively that it becomes a useless, degenerate solution. The penalty keeps it grounded in the original behavior.
Optimization schedule:
An episode here means one generated summary; 1 million episodes means generating 1 million summaries during RL training. Given batch size 512, that's roughly iterations.
Models need fixed-size inputs, but Reddit posts and news articles have variable lengths. Here's how it's handled:
All models use byte-pair encoding (standardized vocabulary from reference [48]). This converts text into token IDs.
Fixed input size: Each example is encoded as a sequence of exactly 2048 tokens (the same 2048 mentioned in position embeddings).
Pad from the beginning (left-padding). This is standard in transformer-based NLP because attention can attend to any position equally, so padding position doesn't matter much. Left-padding slightly helps with batch efficiency.
The text is truncated at newlines to stay under 2048 tokens. This is a soft constraint: rather than hard-truncating in the middle of a sentence, truncate at a natural paragraph boundary (newline character). This preserves semantic completeness better than truncating mid-sentence.
When sampling from models pretrained on the pretraining mixture but not fine-tuned on TL;DR:
Instead of padding with a special [PAD] token, pad with in-context examples:
This is few-shot prompting—the model learns from examples what a good summary looks like, without explicit fine-tuning. It's less effective than fine-tuning but doesn't require task-specific training data.
| Phase | Batch Size | Learning Rate | Epochs | Duration |
|---|---|---|---|---|
| Pretraining | Ramped up | Cosine decay | 1-3 | 200-300B tokens |
| Supervised (TL;DR) | 128 | 1 | ~1 epoch | |
| Supervised (CNN/DM) | 128 | 1 | ~1 epoch | |
| Reward Model | 64 | 1 | ~1 epoch | |
| PPO (RL) | 256-512 | Linear decay from | 4 per batch | 1M episodes |
Learning rates decrease as we go downstream: Pretraining uses larger LRs (you're learning from scratch), supervised fine-tuning uses medium LRs, and RL uses tiny LRs (you're making careful adjustments to a good policy).
Batch sizes vary by task complexity: Pretraining uses large batches (better stability with large datasets), supervised learning uses medium batches, and RL uses large batches again (RL is less data-efficient per parameter update, needs more data per batch).
The KL penalty in RL is essential: Without it, the reward model optimization could push the policy to nonsensical solutions. The penalty says "optimize the reward, but don't deviate too much from supervised learning."
Single-epoch supervised training: Multiple epochs would overfit. One epoch leverages pretraining effectively while adapting to the specific task.
C.1 Process for ensuring high-quality human data. We first detail the procedures we use to ensure high-quality data. Whi...
This section addresses a critical but often overlooked aspect of machine learning: the quality and validity of human feedback data. The paper's entire approach depends on training a reward model to predict human preferences, which then guides reinforcement learning. But this raises a fundamental question: How do we know the human feedback is actually good?
Think of it like this: if you're building a system to learn what humans want, you need to ensure the humans doing the evaluating are:
This section documents their rigorous process for achieving this.
The authors describe a systematic approach to ensure labeler quality. Let me break down what each step accomplishes:
Before asking labelers to do anything, the researchers themselves deeply understand the task. This is crucial because researchers later serve as a "ground truth" benchmark to evaluate labeler agreement.
Labelers are trained on the task through a structured onboarding process. This is like training a classifier: you need to ensure all labelers are calibrated to similar standards before collecting data.
The actual collection of pairwise comparisons between summaries. This is the raw dataset that will train the reward model.
Active feedback to labelers about their performance—showing them where they disagree with researchers and helping them improve. This is an iterative process.
Researchers periodically re-label portions of the data to maintain a consistent ground truth and catch any drift in labeler behavior.
Key insight: Notice the emphasis on "high communication bandwidth." The authors maintain:
This social/collaborative aspect of data collection is often invisible in papers but crucial in practice.
This section contains the quantitative assessment of labeler agreement. Let me define the metrics clearly:
Labeler-Researcher Agreement: Among all comparisons labeled by both a labeler and a researcher (excluding indifference cases), what fraction do they agree on?
Researcher-Researcher Agreement: Among all comparisons labeled by two independent researchers, what fraction do they agree?
The fact that might seem counterintuitive at first. However, this makes sense because:
The authors note agreement ranges from:
This range tells us something important: not all comparisons are equally reliable. In principle, you might want to weight training examples by labeler confidence or agreement levels, though the paper doesn't explicitly mention doing this for the reward model training.
For the complete reward model training corpus, they compute:
Where:
Result: agreement
This is a weighted average, giving more weight to prolific labelers' agreement rates.
The authors include demographic information (Table 5 from the survey) covering:
Key finding: While there's diversity, labelers skew toward White and American.
This isn't just an ethical note—it has concrete implications for the learned behavior:
The reward model learns a function that predicts:
where is an article and is a summary. If your labeler population is not representative, then will be calibrated to the preferences of your specific demographic group, which is a systematic bias.
This is a form of selection bias in the training distribution.
For comparison tasks, labelers evaluate summaries along explicit dimensions:
For Likert evaluations, they use detailed rubrics for:
Mathematical interpretation: Each dimension can be thought of as a separate feature or axis in an evaluation space. The labeler is making a decision in a high-dimensional space:
The specific instructions ensure that is somewhat consistent across labelers.
This subsection addresses an important statistical phenomenon: temporal drift in labeling standards.
Imagine you train a reward model at time on labels collected from labelers, then at time you collect new labels. If labeler standards have shifted, you have a distribution mismatch:
This violates the typical i.i.d. (independent and identically distributed) assumption in machine learning.
They maintain calibration by including "anchor" comparisons in each batch:
If this ratio shifts significantly, it indicates labeler standards have drifted.
They note: "Every time we trained a reward model, we trained on all labels collected so far."
This means:
where batch is collected during iteration . This cumulative approach averages out temporary fluctuations in individual batches.
The key insight is that the quality of the final summarization model is bounded by the quality of the human feedback it trains on:
This is sometimes called the "alignment problem" in machine learning. By carefully documenting:
The authors are ensuring that their reward model is learned from high-quality, consistent, relatively unbiased human preferences. This transparency about data quality is uncommon but increasingly important as ML systems become more influential in real-world applications.
In testing our human feedback techniques, we collected a large amount of high-quality data from human labelers. In order...
This section addresses a fundamental research challenge: how do you fairly compare a new training method against existing methods when you have limited resources? The authors are being transparent about a trade-off they made in their experimental design. They trained models using human feedback (which is expensive), but they didn't have enough budget to also collect human demonstrations for a fully comparable supervised learning baseline. So they explain what baselines they did use and why.
This matters because a paper's credibility depends on whether the comparisons are fair and convincing.
To fairly evaluate their human feedback approach, the authors would have needed to:
The key insight: The amount of labeler effort for both methods should be roughly equal. If Method A uses 100 hours of human labelers and Method B uses 1 hour, the comparison isn't fair—Method A has an unfair advantage from extra human input.
As the authors state: "this is prohibitively expensive." Here's why this constraint exists mathematically:
If we denote the total labeler budget as (measured in hours), and:
Then a fair comparison would require:
But the authors found that collecting enough high-quality demonstrations to match their existing feedback data would exceed their available budget. Rather than proceed with an unfair comparison, they chose to be transparent about this limitation.
The authors compared against three types of models:
These are summarization models trained on the TL;DR dataset using standard supervised learning (predicting human reference summaries).
Why this works as a baseline:
Mathematical framing: If represents supervised loss (typically cross-entropy with reference summaries) and represents the reinforcement learning loss optimizing the reward model, comparing models trained with each loss function shows the benefit of the new objective:
These are pretrained models that have not been fine-tuned on any summarization task.
Why include this? It establishes a lower bound of performance—a sanity check that fine-tuning actually helps.
T5 is a strong existing baseline from prior work with two key differences:
Why T5 matters: It's an independent, well-established method from the literature. If the authors' human feedback approach beats T5, that's evidence their method works—not just that they've tuned their own model well.
The authors mention PEGASUS, a prior work that studied supervised learning on a very similar dataset (the Reddit TIFU subset of TL;DR).
This creates an apples-to-oranges comparison problem. If the authors compared their large models against PEGASUS's small models, any improvement could be attributed to:
Mathematically: The observed improvement would be:
They wouldn't be able to isolate (the contribution of their novel approach) from (the contribution of using bigger models).
The authors' approach here reflects an important principle in machine learning research:
Being explicit about limitations is better than making unfair comparisons.
By stating "we do not provide such a baseline" rather than creating a weak or unfair baseline, they:
| Baseline Type | Why Used | Limitations |
|---|---|---|
| Own supervised models | Same setup, isolates the effect of training objective | Doesn't show benefit vs. completely different supervised approaches |
| Zero-shot models | Lower bound / sanity check | Not competitive |
| T5 models | Independent, well-established method from literature | Different architecture complicates comparison |
| PEGASUS (NOT used) | Similar dataset and task | Different model sizes; wouldn't isolate the method's contribution |
This section teaches us that experimental design requires honest trade-offs. The authors couldn't collect enough human demonstrations to make a perfectly fair supervised baseline, so they used their own models (which isolate their method's contribution) and established baselines (T5, zero-shot) instead. This is more defensible than creating artificially weak comparisons or overstating their results.
As discussed in Section 4.1, the length of a summary is a confounding factor for evaluating summary quality; depending o...
Before we dive into the math, let's understand the core problem this section addresses:
The Problem: When comparing two summarization models, a crucial confounding variable is summary length. Imagine one model produces very long summaries (say, 100 tokens) while another produces short ones (30 tokens). The longer summary might include more information, making it seem "better" — but is that actually a better summary, or just a longer one? Humans naturally prefer summaries that are concise yet comprehensive, and the optimal length depends on context.
The Solution: Instead of directly comparing models, the authors isolate the effect of the model itself by statistically controlling for length. Think of it like this: if we could ask "how would these models compare if they generated summaries of identical length?", we'd get a fairer comparison.
This section explains the statistical technique they use to answer that question.
In statistics, a confounding variable is a factor that affects your outcome but isn't the main thing you're studying. Here:
To control for a confounding variable, we use regression — a fundamental statistical technique you likely learned in college math. The idea: model how the outcome depends on multiple factors, then isolate the effect of the factor we care about.
The authors use logistic regression to predict human preference. Let me break this down:
What they're predicting: For each pair of summaries shown to humans, was summary A or summary B preferred? This is a binary classification problem (two possible outcomes).
What features they use: Two pieces of information about each summary pair:
The logistic regression model has this form:
Let me unpack this equation:
The formula is called the sigmoid function — it's the standard way to convert any real number into a probability (something between 0 and 1).
Why log ratio? Using the logarithm of the length ratio has a nice interpretation: it makes the model approximately linear in log-space, which is often more natural for length comparisons.
The authors train this logistic regression model on their entire dataset of human comparisons. The training process finds values of , , and that best predict which summary humans preferred. This uses maximum likelihood estimation, a standard statistical technique.
Key point: This is a descriptive model — it's learning the empirical relationship between length, policy, and human preference from the data.
Once the logistic regression model is trained, here's the clever bit:
To compare two policies while controlling for length, they:
For policy A compared to policy B, the length-controlled preference becomes:
Notice the term — by setting the length ratio to zero, we're essentially removing length's influence from the prediction.
Interpretation: This answers the question: "What would the preference ratio be if both summaries had the same length?" By setting length to zero, we're asking the model to predict based on policy identity alone.
After computing the length-controlled preference, the authors check whether their findings are robust by examining performance across different summary lengths.
Figure 10b plots:
Key finding: The human feedback model outperforms the supervised baseline across all lengths, not just at the particular length their model happened to use.
Why this matters: This shows that the superiority of the human feedback model isn't just an artifact of length — it's a genuine quality improvement. Even if both models generated summaries of identical length, humans would still prefer the human feedback model.
For the CNN/DM dataset, the authors use a slightly different method:
Instead of logistic regression predicting binary preference, they use linear regression to predict Likert ratings (the 1-7 quality scale):
This is simpler notation — no sigmoid function, just a straight linear relationship.
Why linear instead of logistic?
Table 14 shows: "Expected quality increase for making summaries 100 characters longer"
Mathematically, if their linear regression is:
Then the change in quality from adding 100 characters is approximately:
where is the baseline length. For typical summary lengths, this is roughly proportional to .
Interpretation of Table 14's finding: This quantifies the length-quality trade-off. If their human feedback models would perform better by generating longer summaries, that suggests the task setup (the 24-48 token limit) might not align with the optimal length for quality.
This section addresses a subtle but critical issue:
Without length control, you might conclude: "Model A is better because humans prefer it more."
But the truth could be: "Humans prefer Model A more because it's longer, not because it's actually higher quality."
By controlling for length, the authors demonstrate that their human feedback models are genuinely better at the core task — not just better at gaming the preference signal by making longer summaries.
Connection to the main paper: This connects back to the central theme: they're optimizing human preferences, but they need to ensure those preferences reflect actual quality improvements, not artifacts of how the preference signal correlates with other factors.
| Concept | Meaning |
|---|---|
| Confounding variable | A factor (length) that affects the outcome (preference) but isn't what you're studying (model quality) |
| Logistic regression | A statistical model for predicting binary outcomes (A vs B) using multiple features |
| Sigmoid function | — converts any number into a probability |
| Setting length ratio to zero | Mathematically isolating the effect of policy by removing the length variable's influence |
| Length-controlled preference | The answer to: "How much would humans prefer this model if both models generated summaries of identical length?" |
| Linear regression | Statistical model for predicting continuous values (like 1-7 ratings) |
The authors use regression analysis to statistically separate the effects of:
This ensures their conclusion — "human feedback training produces better summaries" — is valid and not just an artifact of length differences.
G.1 Value function ablation. In this section, we conduct an ablation comparing using separate parameters for the value f...
Section G presents supplementary experimental analyses that validate and deepen our understanding of the paper's main findings. Rather than introducing new methods, this section asks: "How robust are our results? What hidden aspects of our approach work best? Do our metrics actually measure what we think they measure?"
Think of this as "deep diving" into the mechanisms behind the paper's success. The authors want to ensure readers understand not just that their approach works, but why and how broadly.
In reinforcement learning (RL), there are typically two neural networks:
The question here is: Should these be separate networks or share parameters?
Let's denote:
Two architectural choices:
The authors report that separate networks clearly outperform shared networks. However, there's a trade-off:
Advantages of separate networks:
Disadvantages:
This is clever: Since the reward model estimates summary quality, it's a reasonable starting point for . The value function can then be fine-tuned during RL training. This is more efficient than random initialization.
Rather than a single quality score, human evaluators rated summaries on multiple axes:
Each evaluation is a number from 1-7 on this ordinal scale.
For a given summary and evaluation dimension , let:
The key finding from Figures 12 and 13 is expressed statistically as:
Coverage has the strongest correlation with overall score.
In mathematical terms, if we compute the Pearson correlation coefficient between coverage scores and overall scores:
This is important because it tells us which aspects matter most to human judges.
Since all models achieve high coherence, the difference between models comes primarily from coverage and accuracy—what information is included and whether it's correct. This validates why the reward model, trained to match human preferences, would emphasize coverage.
Here's the fundamental principle: A good evaluation metric should correlate with human preference when optimized.
The experiment works like this:
ROUGE (baseline metric): Computed as word overlap between generated and reference summaries:
\text{ROUGE} = \frac{\text{# overlapping n-grams}}{\text{# total n-grams in reference}}
Reward model : Trained on human preferences as described in the main paper.
For RL policies (PPO in particular), there's a trade-off parameter controlling deviation from the baseline:
Where:
As increases (more optimization):
Why? ROUGE is a proxy metric that doesn't perfectly align with human preferences. Over-optimizing a poor proxy leads to increasingly unnatural summaries. The reward model, trained on human data, maintains alignment.
ROUGE computes n-gram overlap. For bigrams (2-word sequences):
Where is the frequency of bigram .
On TL;DR: Human feedback models get lower ROUGE scores than supervised baselines, yet humans prefer them.
This is the paper's central message: ROUGE is a poor proxy for quality.
On CNN/DM: ROUGE actually agrees with humans here.
TL;DR summaries can be abstractive (rewritten), so copying reference n-grams isn't necessary for quality. CNN/DM news articles benefit more from extractive summarization (copying relevant sentences), so ROUGE captures more of what matters.
Define the copy rate as:
\text{CopyRate}(s) = \frac{\text{# bigrams in } s \text{ that appear in source}}{\text{# total bigrams in } s}
This uses longest common subsequence (LCS) of bigrams.
Models fine-tuned on human feedback copy less than purely supervised models. This suggests they're learning to paraphrase and abstract better, not just regurgitate source material.
The authors created specially constructed test cases to check if is actually learning meaningful features:
Test 1: Sentence Shuffling
Test 2: Role Switching
These tests show learns about semantic coherence and correctness, not just surface-level n-gram statistics.
Table 19 provides qualitative examples where small semantic changes matter to the reward model but not ROUGE.
For comparing different metrics, we compute how often they rank summaries the same way. Formally, for metrics and , agreement is measured by correlation:
across all summaries in the evaluation set.
Reward model agreement with humans: The 6.7B reward model achieves agreement comparable to labeler-labeler agreement (both ~73%)
Ensemble of labelers: Still better than single reward model, suggesting room for improvement
ROUGE agreement: Poor across the board, validating that ROUGE is unreliable
Baseline policy log-probability: Also poor agreement
Simple heuristics: Length and copying frequency sometimes match ROUGE's agreement levels, indicating ROUGE may be dominated by these simple statistics
If we denote agreement as :
This validates the entire approach: training on human feedback (via the reward model) provides better guidance than standard metrics.
Together, G.1–G.7 establish:
This transforms the main paper's claim from "we got good results" to "we did it the right way, and we can prove our metrics work."