Skip to main content
Gildea verifies every unit before serving it. This page is our evaluation of what comes out the other side: is a served unit faithful to what its source said? It reads each served unit against its cited source, looks for seven kinds of error, and hands you a queue of anything material, for you to review. Run it yourself on any slice of what we serve. You never have to run this. Every unit is already evaluated before we serve it, and that is where the faithfulness number we report comes from. We publish the method so you can prove it to yourself, on your own data, rather than take our word for it.

What it checks

Most verification stops at “is the quote real”. That is the easy part, and it is not where synthesized text goes wrong. A sentence can carry a perfectly real quote and still mislead. So the evaluation reads each unit against its full cited source and looks for seven kinds of error, six of them subtle hallucinations that survive a citation check: Every check compares one served sentence against its own source article. Nothing is judged across articles or against outside knowledge. Three rules keep the evaluation honest:
  • A wrong fact is the zero bar. A number, date, or fact the source contradicts is the most serious error. It is reported separately from the subtle hallucinations; there should be none.
  • Attribution is wrong-speaker only. Naming the wrong person, or crediting the author for a quoted speaker’s line, is an error. A claim served with no speaker, or as a plain statement of fact, is not.
  • Materiality is a before-and-after test, not a verdict. An error counts only if it changes what a reader concludes. You settle that by rewriting the unit faithfully and comparing what a reader takes away from the served version versus the corrected one, both with the citation in hand. Same takeaway, it is style; different takeaway, it is material. A wrong fact is always material.
One class this can’t catch: a unit whose text is faithful but whose entity tag points at the wrong company or person. No single source can expose that. Gildea handles it upstream with entity resolution.

Set up the check

Install gildea and anthropic, set GILDEA_API_KEY and ANTHROPIC_API_KEY, then:

Calibrate the judge first

A judge you have not tested is a judge you cannot trust. Before we read a single real verdict, we test ours on four dimensions. You should too:
  • Clear-cut accuracy. Does it flag an obviously broken unit and pass an obviously clean one? The floor; a judge that fails here is broken.
  • Hard-case accuracy. On genuinely ambiguous calls, does it reach the verdict a person already settled on? This is where a judge quietly skews too strict.
  • False negatives. Does it catch a material error dressed up to look harmless? Reviewing flags can’t tell you this: you only ever see the errors the judge caught, so anything it missed never reaches you. The only way to measure misses is to plant errors you know are there and check they get flagged.
  • Stability. Does the same unit get the same verdict twice?
The first and last you can run directly:
The other two, hard-case accuracy and false negatives, need cases you author by hand. For hard-case accuracy, take a handful of units you have already judged yourself and confirm the judge agrees. For false negatives, plant material errors disguised as harmless, a hedge quietly flipped in an otherwise clean sentence, a speaker swapped mid-paragraph, and confirm the judge both flags them and rates them material. If it clears one, tighten the prompt before you trust the run.

Run it on a sample

Point it at any slice: a query, or scope by entity, theme, or time window.

Review the flags

An automated judge is fallible, and it tends to over-flag: it calls things errors that a careful read finds harmless. So the output is a queue, not a score. For each flagged unit, read the two takeaways against the source passage and decide for yourself whether the difference would actually move a reader. You will clear some of them. The rate that means anything is the one you confirm by hand.

What you get

A per-unit account of every material error, its faithful correction, and where in the source it settles, on any slice you choose. This is the same evaluation we hold our own pipeline to. Our internal runs add two things this recipe leaves out: a cheap evidence-only first pass before fetching the source, and a 95% confidence bound on the rate. The checks themselves, the seven kinds and the materiality test, are identical. If your review surfaces a unit we missed, we want it: email your findings to ops@gildea.ai.

How verification works