06-reference/concepts

llm eval review types and harnesses

2026-11-06·synthesis·source: Anthropic eval course and docs (founder study notes, iMessage 2026-11-06) plus Ray synthesis·by Ray (synthesis); categories from Anthropic course material
llm-evalsllm-as-judgeeval-harnesshallucinationcert-study

LLM eval review types, off-the-shelf harnesses, and hallucination fixes

Mental model in one line: grade with code wherever you can, use an LLM judge where you must, and use humans to calibrate the judge. A harness is just dataset → task → scorers → report, run on every change.

Why this is in the vault

The founder is studying evals for the Claude cert track and for client work. He asked for one place to look these categories up later. These are the reference lists, with the distinctions most likely to be tested.

1. Three types of eval review (Anthropic course)

Type Best for Cost and speed Notes
Code-graded Anything with a checkable right answer Fastest, cheapest Exact match, regex, string contains, "does it parse as valid JSON / match the schema", numeric tolerance. Push as much as possible into this tier.
LLM-as-judge Subjective or fuzzy quality (tone, helpfulness, faithfulness) Middle Only as good as the rubric: specific criteria, a pass/fail or small fixed scale, reasoning before the score, a judge prompt separate from the one that produced the output.
Human review Ground truth, high-stakes calls Slowest, most expensive Its best use is calibrating the LLM judge: label a sample, check that the judge agrees, then trust the judge at volume.

2. Five ways to make unsupported answers (hallucinations) rarer

This is the five-item list from the founder's eval course. It draws on the Anthropic docs page linked above, which splits strategies into three "basic" ones (items 1-3) and four "advanced" ones (items 5 and 6 below, plus chain-of-thought verification and best-of-N verification). Item 4 is not on that page.

  1. Let it say "I don't know." Tell the model it may admit uncertainty. The docs' example is "I don't have enough information to confidently assess this." For structured output, the course example returns null.
  2. Quote before answering. Extract the supporting quotes first, then answer only from them. The docs scope this to long documents (>20k tokens). It works before the answer: it prevents bad claims.
  3. Cite back to the document. Answer, then find a supporting quote for each claim and retract any claim without one. It works after the answer: it audits claims and leaves a trail a human can check. (Separately, the API has a built-in Citations feature for document inputs that returns the cited passages. That comes from the API docs, not this page.)
  4. Add a verification pass. A second request checks the first answer and returns a verdict. The closest item on the docs page is "iterative refinement". It becomes the evaluator-optimizer pattern (a term from Anthropic's agent-pattern guidance, not this page) only when the verdict feeds a rewrite, in a loop.
  5. Restrict outside knowledge. Answer from the document alone, not from training data. The docs list this under advanced, as "external knowledge restriction".

The docs also list two more advanced techniques:

Memory hook: IDK and restrict-knowledge set the rules. Quote-first grounds the answer. Citations audit it. Verification double-checks it.

3. Off-the-shelf eval harnesses

Every harness has the same shape:

  1. Dataset: test cases (inputs, plus expected outputs or reference answers where they exist).
  2. Task: the prompt + model (+ tools) under test.
  3. Scorers: code checks, LLM-judge rubrics, and hooks for human labels.
  4. Runner and report: run all cases, aggregate pass rates, compare against the last version, and ideally gate CI or a deploy.

Common options. These are from Ray's general knowledge, not checked against current vendor docs:

Mapping against Ray Data Co

Open questions

Related