Skip to content

LLM Evaluation and Benchmarks

How we measure what language models can do: standardized benchmarks, human preference comparisons, model-graded tests and task-specific evals, each with its own blind spots.

Also benchmarks · MMLU · LLM-as-a-judge · evals · Chatbot Arena · benchmark contamination

Fig. / How it works
Test questionsTest questionsModel answersModel answersGrade the answersGrade the answersScoreScore
Role · kind
Evaluating and testingConcept
Level
Intermediate

Grading a student who can write about anything. Multiple-choice tests are easy to score but limited, essays need a grader, and if the student has seen the test before the score means little.

Where it fits

+All relationships as a list

See it on the full map

How it works

For a classifier, accuracy on a held-out test set settles most questions. For a model that can write anything, evaluation is much harder.

The main approaches:

  • Static benchmarks. Fixed question sets with checkable answers: multiple-choice knowledge tests (such as MMLU), math problems with exact answers, coding tasks verified by unit tests. Cheap and reproducible.
  • Human preference. People compare two anonymous answers and pick the better one; many comparisons produce a leaderboard ranking. Captures overall helpfulness, but also rewards style and length.
  • LLM-as-a-judge. A strong model grades answers against a rubric. Scales well, but judges have biases, for example favoring longer answers or their own style.
  • Your own evals. A set of real tasks from your application with clear grading. Usually the most informative.

Watch out for:

  • Contamination: benchmark questions leak onto the web and into pretraining data.
  • Saturation: top models score near 100%, so the benchmark no longer separates them.
  • Goodhart’s law: once a number becomes a target, it stops measuring what you care about (compare reward hacking).

Evaluation also covers safety: red teaming probes for harmful behavior that standard benchmarks miss, and hallucination rates need their own tests.

Everyday use cases

  • Case 01

    Choosing a model for a product

    A team runs 200 real customer questions through three models and grades the answers before deciding.

  • Case 02

    Catching regressions

    An eval suite runs on every prompt change so improvements in one area do not silently break another.

Strengths, weaknesses and when to use it

Strengths

  • Good evals make progress measurable and model choices defensible.

Weaknesses

  • Public benchmarks leak into training data and saturate quickly; scores rarely match your specific use case.

When to use itBefore choosing or changing a model or prompt. Build a small eval set from your own real tasks.

Compare with

Check yourself

  1. Q01

    What is benchmark contamination?

    Show answer

    A: Test questions appearing in the model's training data, inflating its score

  2. Q02

    Which is the most reliable way to judge a model for your own application?

    Show answer

    A: A test set built from your real tasks, graded carefully

Go deeper