DPO Variants › Conservative DPO (cDPO)
Language AI HandbookAll chapters DPO Variants › Conservative DPO (cDPO)One section · Sections in this chapter5 / 12 ↓
Reading tools Definitions & inline links
Choose your expertise level to adjust how many terms are explained. Beginners see more tooltips, experts see fewer to maintain reading flow. Hover over underlined terms for instant definitions.
Article links
Make inline references clickable
The variants discussed so far address algorithmic limitations. cDPO, introduced by Mitchell et al. (2023), addresses a data quality issue: label noise in preference annotations. While IPO and ORPO assume that the training labels are reliable (even if the optimization dynamics are problematic), cDPO starts from the recognition that human annotations are inherently uncertain and builds that uncertainty directly into the loss function.
Think of cDPO as the difference between a GPS that reports its location with false precision and one that reports a confidence interval. Standard DPO says "response A is better than response B, and that fact is certain." cDPO says "response A is probably better than response B, with probability ." The probabilistic framing leads to a fundamentally different loss landscape with a bounded optimal preference gap rather than an infinite one.
Label Noise in Preference Data
Human preference annotations are inherently noisy, and this noise can arise from several sources. Annotators may disagree with each other on the same comparison, make mistakes due to fatigue or inattention, apply inconsistent criteria across examples, or be influenced by surface features such as formatting and length rather than actual quality differences.
Studies of inter-annotator agreement on preference tasks typically show agreement rates of 70 to 80 percent, meaning 20 to 30 percent of labels may be "wrong" in the sense that a different annotator would have labeled them oppositely. Even gold-standard human annotations on tasks like toxicity detection or factual accuracy show substantial disagreement when the same examples are labeled by different annotators. The problem is not that annotators are careless; preferences are subjective, and the ranking of two similar responses is often not clear-cut.
Standard DPO treats all preference labels as ground truth. If the training data says , the model learns to prefer with full confidence. When this label is wrong, the model learns an incorrect preference, and because DPO's unbounded optimization pushes that preference to an extreme, even a small percentage of mislabeled examples can cause significant downstream problems. The model in effect memorizes the noise in the data and tries to push it to infinity.
Label Smoothing for Preferences
cDPO applies label smoothing to preference labels. The idea behind label smoothing is familiar from classification: instead of training on hard targets (0 or 1), we train on soft targets that acknowledge uncertainty. For preferences, instead of treating each comparison as a certainty, we model the possibility that the annotation might be wrong.
Instead of treating preferences as deterministic (), cDPO models uncertainty:
where:
- : the label smoothing parameter, , representing uncertainty about annotation correctness
The parameter is our belief about how often the annotations are wrong. If , we trust all annotations completely, recovering standard DPO. If , we believe that 30 percent of the time the annotators got it backwards and the rejected response was better.
The cDPO loss modifies the Bradley-Terry model probability accordingly:
where:
- : the cDPO loss function
- : the expectation over the dataset
- : the log-ratio difference between chosen and rejected responses
- : the label smoothing parameter
- : the sigmoid function
- : the temperature parameter
This loss function has two terms. The first term, weighted by , is the standard DPO loss: it rewards the model for preferring the labeled chosen response. The second term, weighted by , is the opposite: it rewards the model for preferring the labeled rejected response. The combination is the expected loss under our belief about annotation accuracy. We train the model to do well on average across both the case where the annotation is correct and the case where it is wrong.
Using the identity , we can rewrite this loss to explicitly show the probability mass assigned to the rejected response:
where:
- : the probability assigned to the rejected response (equivalent to )
- : the weighting factor for the "incorrect" preference direction
This form makes the label smoothing interpretation particularly clear: we are mixing the standard DPO loss with its inverse, with the mixing coefficient representing the probability of annotation error.
Effect on Optimization
Label smoothing fundamentally changes the loss landscape. The gradient of cDPO with respect to is:
where:
- : the gradient of the loss with respect to the log-ratio difference
This gradient has two competing terms. The first term pushes toward larger (stronger preference for chosen). The second term pushes toward smaller (acknowledging that the rejected response might be better). These competing forces create a balance point where the gradient is zero.
Setting the gradient to zero allows us to solve for the optimal log-ratio difference :
where:
- : the optimal value of the log-ratio difference
- : the label smoothing parameter
This means cDPO has a finite optimal gap (similar to IPO), which depends on . With standard DPO (), the optimal gap is infinite. With cDPO (), the model converges to a bounded preference strength. The relationship between and the optimal gap is intuitive: higher annotation uncertainty (larger ) leads to a smaller optimal gap, because the model should not be confident when the labels might be wrong.


Choosing the Smoothing Parameter
The smoothing parameter should reflect actual annotation noise. When inter-annotator agreement data is available, can be estimated directly as the disagreement rate. When that data is unavailable, practical guidelines based on dataset characteristics give reasonable starting points:
- : Assumes 90% annotation accuracy, appropriate for high-quality curated datasets with expert annotators.
- : Assumes 80% accuracy, appropriate for crowd-sourced annotations where annotators receive limited instructions.
- : Assumes 70% accuracy, appropriate for noisy or automated annotations generated by another model.
The effective training signal strength scales with . At , the signal is 80% as strong as standard DPO. At , it is only 40% as strong. This means that high smoothing values require more training data or more epochs to reach the same degree of preference learning, creating a practical trade-off between robustness to noise and data efficiency.