Judge Calibration
Calibrating the Judge
Section titled “Calibrating the Judge”In high-stakes research, the LLM Judge is a source of potential variance. Even with clear rubrics, different models (or the same model at different temperatures) can produce inconsistent scores. AgentV provides tools to calibrate these judges, ensuring that your research results are stable and verifiable.
Why Calibration Matters
Section titled “Why Calibration Matters”- Inter-Rater Reliability: Ensuring that if you swap from GPT-5.4-Mini to Claude-4.6-Sonnet as your judge, the fundamental grading criteria remain consistent.
- Evaluation Drift: Detecting if updates to the judge model (e.g., a new “v2” release) silently change how your historical traces are scored.
- Sensitivity Analysis: Understanding how sensitive your aggregate WSM score is to minor changes in the judge’s prompt.
The Calibration Protocol
Section titled “The Calibration Protocol”AgentV recommends a three-step calibration protocol for academic publications.
1. Zero-Temperature Baseline
Section titled “1. Zero-Temperature Baseline”Always set LUNA_JUDGE_TEMPERATURE=0.0 for production research. This forces the judge to use the most deterministic tokens, significantly reducing variance across runs.
2. Stability Benchmarking
Section titled “2. Stability Benchmarking”Execute the same evaluation trace through the judge 10 times. AgentV calculates the Stability Index:
- Index > 0.95: High stability; suitable for publication.
- Index < 0.80: High variance; requires rubric refinement or a more capable judge model.
3. Model Head-to-Head
Section titled “3. Model Head-to-Head”Run the same batch of 100 traces through two different judge models (e.g., openai://gpt-5.4-mini and ollama://llama4). If the correlation between their scores is below 0.90, the rubric is likely too ambiguous and needs further specialization.
Advanced: Bayesian Judge Aggregation
Section titled “Advanced: Bayesian Judge Aggregation”For extreme rigor, researchers can use Consensus Evaluation. This involves:
- Scoring a trace with 3 distinct judges (e.g., Gemini, GPT, and Claude).
- Using the
consensusmetric to identify outliers. - Automatically flagging traces where judges diverge significantly for manual human-in-the-loop (HITL) review.