Skip to content
Clairos Learn

Evaluations and datasets · Lesson 12 of 18 · 9 min

Find annotation disagreement

Annotation disagreement can reveal an ambiguous rubric rather than a model defect. Resolve the criterion and preserve adjudication notes before using the label as ground truth.

Mastery 0/3Run itExplain itApply it
learner@clairosSimulated AI Ops lab
learner@clairos:~ $
↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Understand the pattern

Annotation disagreement can reveal an ambiguous rubric rather than a model defect. Resolve the criterion and preserve adjudication notes before using the label as ground truth.

Interpret the evidence

Clarify and adjudicate the ambiguous rubric before treating either label as definitive.

A tempting mistake

Always discard the stricter reviewer without checking the criterion.

All names, measurements, prices, versions, and thresholds in this exercise are fictional training data. The evidence supports this bounded scenario, not a claim about a live provider.

Worked example and expected result
$ cat /opt/ai-lab/cases/aiops-evals-datasets-012.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "case": "case-009",
  "reviewer_a": "pass",
  "reviewer_b": "fail",
  "rubric_ambiguous": true
}

Exit status: 0. The command completed successfully in the training fixture.

$ jq .rubric_ambiguous /opt/ai-lab/cases/aiops-evals-datasets-012.json
true

Exit status: 0. The command completed successfully in the training fixture.

$ printf '%s\n' 'clarify-rubric' > /home/learner/lab/aiops-evals-datasets-012-decision.txt
(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Name the assumption that would have to change for “clarify-rubric” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Find annotation disagreement” justify?

Apply it elsewhere

A colleague concludes: “Always discard the stricter reviewer without checking the criterion.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Detect evaluation leakageTry an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

  1. 01Inspect a data sliceSlice evaluation checks behavior on a meaningful subset. Keep slice size with the score and avoid generalizing a small or unrepresentative slice to all traffic.Practice
  2. 02Detect evaluation leakageEvaluation leakage happens when held-out information influences tuning or selection. A contaminated test set can exaggerate generalization performance.Practice
  3. 03Review dataset provenanceDataset provenance records origin, permission, transformations and version. Without it, a technically valid file may still be inappropriate or impossible to reproduce.Practice