Preference pair: name the two pieces and what the label expresses.
Same topic, related formats. Practice these next.
Same topic, related formats. Practice these next.
A preference pair is one prompt plus two responses, one chosen and one rejected. The label is relative ordering, not absolute correctness.
Imagine two restaurants serve you the same dish on the same evening. You are not asked which dish is objectively good; you are only asked which one you preferred tonight. That single comparison is the preference pair. There is no grade sheet, no answer key, no rubric saying either plate was right or wrong. The teaching signal is just the ordering between the two. Training systems that learn from these comparisons (the most famous is DPO) only need that ranking. They never claim the chosen plate was perfect or the rejected one was inedible. The labeller's job is simple: pick one of two, and the model figures out the rest from many such picks.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
5 min: the three fields of a preference pair + why the label is relative + how the data gets generated + which losses consume the triple + length bias and tie handling.
Real products, models, and research that use this idea.
What an interviewer would ask next. Try answering before peeking at the approach.
Red flags and common mistakes that signal junior thinking. Click to expand.
Reading the chosen response as the gold answer the model must memorise. The label only encodes ordering; the chosen response can still be flawed in absolute terms, just less flawed than the rejected one.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.