Fact check
Which facts engines state wrongly about you, in one table, and where your corrections to each provider stand.
Overview
The Fact check answers two questions: which of the facts you hold do answer engines contradict, and what have you done about it? The accuracy judge checks every captured answer against the facts in your Claim library; this page shows the contradictions one fact per row and carries the correction workflow — provider-specific templates, submission, resolution — underneath.
The first line
The page opens by stating what its numbers rest on: the window in capture cycles (for example C12–C15 · 4 cycles, 3 with checks), then how many answers were checked against how many recorded facts. Two cards follow:
- Questions with a contradicted answer — of the questions whose answers were checked, the share with at least one answer contradicting a fact, with the number of answers checked beside it. This card follows the page's lens.
- Facts contradicted — how many of your recorded facts at least one checked answer contradicted. Counted across every question, whatever the lens, because accuracy checks are not stored per question; the card says so.
A read that fails shows "could not load", never a zero — a number that did not come back is not a clean bill of health.
The one facts table
One row per recorded fact a checked answer contradicted in the window:
| Column | What it holds |
|---|---|
| Fact | The fact key and the truth you recorded. |
| What engines say | One example of what an engine said instead — an example, never a canonical value. |
| Engines | The engines that got it wrong. |
| Contradicted in | How many checks contradicted it. |
| Last seen | The capture cycle (C64) the newest contradiction landed in — the same numbering every chart uses, counted from your first capture. |
| Status | The fact's sign-off state in the Claim library. |
| Correction | Drafts a correction pre-filled with the fact and the wrong claim. |
Opening a fact from the Claim library's "→ Fact check" link narrows the table to that one fact (?fact=<key>); Show all widens it again. A fact nothing contradicted in the window says so rather than showing an empty table without explanation.
Drafted corrections link back to the check that found them when that check is among the newest hundred checks in the window — the page reads the most recent hundred and says so under the table.
Correction workflow
Each correction follows a four-stage lifecycle, shown in the Corrections card with a status filter and the counts of each stage:
- Draft — a template is generated with the brand name, the incorrect claim, the correct information, an authoritative source URL and the date observed, formatted as a correction request.
- Submitted — after you submit through the provider's feedback channel, mark it submitted.
- Resolved — when later answers show the error fixed, mark it resolved.
- Reappeared — if a resolved error resurfaces, mark it reappeared and re-submit.
Supported providers
| Provider | AI product | Feedback channel |
|---|---|---|
| OpenAI | ChatGPT | Thumbs-down feedback on responses |
| Gemini | "Report a problem" link in responses | |
| Anthropic | Claude | In-interface feedback button or support contact |
| Perplexity | Perplexity AI | "Report" button next to answers |
| Microsoft | Copilot | Feedback button or Bing Webmaster Tools |
Each generated template carries the provider's own submission instructions.
Tips for effective corrections
- Include authoritative sources — corrections with URLs to official documentation are more likely to be acted upon; the draft pre-fills the fact's evidence URL when one is recorded.
- Be specific — quote the exact incorrect claim and give the precise correct information.
- Submit to every engine that got it wrong — the Engines column tells you which.
- Follow up — if a correction is not addressed within 4–6 weeks, resubmit with newer evidence.
- Keep your facts current — the accuracy check can only compare answers against what you have recorded and approved.
Plan requirements
The Fact check is available on all plans that can capture answers (no separate feature gate).