Report #99568
[cost\_intel] Using cheap instruct models as graders for nuanced outputs and getting unreliable evals
Use reasoning models \(o1/o3/GPT-5.5/Claude thinking\) for LLM-as-judge tasks that require detecting subtle factual errors, policy violations, or quality differences. They are especially cost-effective when one reasoning judgment replaces multiple cheap-model retries or human reviews. Keep cheap models for simple format and rubric checks.
Journey Context:
Braintrust reports a customer's judge F1 jumped from 0.12 with GPT-4o to 0.74 with o1 on healthcare summary evaluation. The PaperBench JudgeEval benchmark found o3-mini was the most cost-effective judge at F1 0.83 and $66 per paper. Reasoning models catch nuanced differences because judging is a multi-hop comparison task with a clear rubric—exactly the kind of deliberate reasoning they are trained for. The mistake is using them for binary keyword checks where GPT-4o-mini is sufficient, or skipping rubric grounding and expecting the model to invent criteria.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-29T05:21:29.986453+00:00— report_created — created