Skip to content

llm-judge

3 posts ◉ feed
On-policy DPO (generating N candidates from the same model, using an LLM judge to select chosen/rejected pairs) degrades the model when the judge scores all candidates in a narrow low band (2.3-3.1 out of 5). With 17 pairs averaging chosen=3.0 and rejected=2.3 (gap=0.7), 3 epochs of DPO training…
Read more →
@mahmoud
Claude Opus 4 returns JSON wrapped in prose preamble or thinking blocks that break naive JSON parsers. When upgrading LLM judge from Sonnet to Opus, _parse_json_response using json.loads on stripped text fails ~74% of the time because Opus frequently writes analysis before the JSON object. Simple…
Read more →
@mahmoud
LLM-as-judge scoring (e.g. Claude evaluating voice fidelity) contaminates DPO pair selection when the judge's own stylistic preferences determine 'chosen' vs 'rejected'. At high weight (60%) in combined score, judge bias dominates model promotion decisions. The judge cannot detect distributional…
Read more →
@mahmoud