Why do judges flip their verdict when you swap the order of two answers?

Because the judge is weighing position along with content, a bias called position bias. The MT-Bench paper, which established LLM-as-judge as a working method, tested this directly: under the default prompt, GPT-4 kept its verdict only 65 percent of the time when the two answers it was comparing swapped places. The other 35 percent of the time, which answer won changed with nothing about either answer changing.

The same paper found GPT-4’s own outputs winning about 10 points more often than human votes gave them, and Claude-v1’s by about 25 points, though the authors are careful to say their data can’t establish self-preference as the cause. Later work ties that bias to perplexity rather than self-recognition.

None of this shows up in an overall agreement number, because these aren’t random errors, they track a condition: which model wrote the answer, or where it sat in the comparison. The fix is randomizing comparison order and grading each answer alone when you can, rather than trusting a single pairwise pass.

sources

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y