Skip to content
DIXON.AI The AI Reliability Tracker
Menu

How we test

How we check AI answers

ChatGPT was sure of a wrong answer on all three tries, and the drawing shows the bench that caught it.

The ten questions, fixed 2 Oct 2026

The test bench, drawn Ten fixed questions go to six AI apps, three tries each in a fresh chat, up to 12 minutes a try. All 180 answers are screenshotted, marked against a key written before any app was asked, a share is marked again by a grader from another lab, and every answer stays on record. 10 QUESTIONS fixed 2 Oct 2026 3 published · 7 private 3 tries, fresh chat up to 12 min a try SIX APPS, AS SHIPPED 180 TRIES, ALL SCREENSHOTTED THE KEY written before any app was asked 2ND GRADER another lab, never Claude DRAWING 1 · TEST BENCH EVERY ANSWER ON RECORD dixon.ai · question set 1 SCALE 1 RUN
The test bench, drawn: every label is a fact of the method below.

Key facts

Apps
6: ChatGPT, Claude, Copilot, Gemini, Grok, Perplexity
Questions
10 fixed: 3 published, 7 kept private
Tries
3 per question, in a fresh chat
When
Monthly, and after a major model launch
The graders
Checked themselves

Four steps, every run.

  1. Ask. Ten questions, three tries each, in all six apps, with a screenshot of every answer.
  2. Mark. Against a key written before any app was asked.
  3. Check. A grader from another lab marks a share again before the report goes out.
  4. Publish. The scores, every miss named in words, every answer on record.

The six: ChatGPT, Claude, Copilot, Gemini, Grok and Perplexity. Run 1 was asked from Sat 3 Oct.

The same conditions for every try
  • A fresh chat, checked empty before typing, in temporary or private mode wherever the app offers one.
  • The question pasted word for word and read back before sending. No follow-up.
  • Each app's default model, left alone and recorded. Web search is left to the app, never forced, and noted on every answer.
  • From run 2, all six apps run on their free plan, signed in, and the plan and model each showed on the day are printed beside its score. Three are Ben's own long-standing accounts; the other three are new accounts made for the test. Run 1 was a pilot on mixed plans: ChatGPT logged out, Claude on Max, Perplexity on Pro.
  • Up to 12 minutes per attempt (15 for the drawing task), then one retry in a fresh chat. Never a third. Run 1 began with 4 minutes, which cut Grok off mid-search on most of its empty tries, so all 30 of Grok's tries are asked again under 12.
Also each month: a showcase, outside the score

Two weeks after each run, one creative task, the same prompt to every app, shown as it came: one try each, no rerolls. It never touches the truth score.

Three published, seven sealed.

Ten questions: three open cards, seven sealed envelopes
One per question: 3 open cards, 7 sealed envelopes.

Published: the question, the answers and the key, every run

  • T02Your own e-scooter: can you ride it on the road or the pavement?
  • T05The planet with the most moons, and exactly how many
  • T06ETIAS for a weekend in Paris

Sealed: the topic, not the wording, until each one retires

  • T01How many bank holidays England has in 2027, with the dates
  • T03A tenant given a no-fault eviction notice in September 2026: is it valid?
  • T04Paternity leave for an employee who has just started a new job
  • T07A Highway Code question about footwear
  • T08A night shift that crosses the October 2026 clock change
  • T09Towing speed limits, with a link to the official page
  • T10Shakespeare's date of birth

A sealed question's exact wording stays private until it retires, after 12 to 26 weeks, and then we publish it word for word. The published answers repeat some of its facts, so every try is checked for a link back to this site.

One of the sealed ten, by its public description: A Highway Code question about footwear. It produced run 1's oddest answer: ChatGPT replied “97”, and nothing else, on 3 of 3 tries. Marked wrong (went along with a false premise), and still 22 of 30 right in run 1.

Ninety-seven what? It didn't say.

Proof the sealed questions weren't changed

Before the first capture we published a fingerprint (SHA-256) of all seven sealed questions and their marking:

3b73efde137bea76e45abdd6234940b9f0bcad1e554e6b4035a21491d79e2ad6

Once a question retires, anyone can hash it and see that neither the question nor its key changed after the answers came in. Check all seven fingerprints

When a question or its key changes

Open keys can move with the law, so each one is re-read at its official source before and after every capture. A change is logged and marked on the chart.

When sealed questions rotate, no more than three change in a run, and a change is only ever called on questions asked in both runs.

Only a right answer scores.

Right
The right answer for the facts in the question. Scores 1.
Wrong
Scores 0, with the reason printed beside it, such as out of date or too early.
Nothing came back
The app errored, never finished or would not run it. Never called wrong, but it counts against the score.
Each reason for wrong

Each try gets one mark, read from what the answer concludes. Misses are never lumped together.

  • Out of date: the old rule, after it changed.
  • Too early: a new rule, before it starts.
  • Went along with a false premise: the question assumed something untrue and the answer did too.
  • Stated as certain when it is not known: the honest answer is that nobody knows.
  • Hedged, but never said it is not known: doubt without the plain answer.
  • Never applied it to the question: the right rule, never brought to the facts asked about.
  • Could not back it up with an official link: for the question that asks for one.
  • Did not answer the question: background, a refusal, or two answers without picking one.
Right, but something wrong in passing

An answer can get the question right and a side fact wrong. It still scores, and the slip is named in words under the scores. Only side facts on a list fixed before the capture count, so nobody can go hunting afterwards.

Why no half marks

Every question gives the facts a right answer needs, so a right answer was always possible. Where the honest answer is that nobody knows, saying so is the right answer.

Right out of every try, with the gaps in words.

Each app's big number is its right answers out of all 30 tries, so a try that came back with nothing counts against it. Beside it, every gap is named in words, then its score out of the answers it gave.

Too few answers
Fewer than 10 of an app's 30 tries came back with an answer. Its row still shows right out of all 30, but no score out of the answers it gave, and no change is called for it in that run.
Pending re-run
The app would not run a try, for example because of a usage limit or a human check. A try like that may be run again within 48 hours of the capture, and shows as pending until then. A run that merely looks bad is never re-run.
What else is printed beside every score
  • The plan and model the app showed that day.
  • Its misses by type, so "most of its misses were out of date" is one glance away.
  • Clean answers: right, with nothing wrong said in passing.
  • How many of its answers a second grader marked again, and how many it agreed with.
  • Any answer that cites this site, marked and shown with a note.

Claude is one of the six, so a grader from another lab checks the marks.

First mark
Claude marks every answer. Four questions are marked by a script first, and each script result is checked.
Second read
A model from another lab, none of the six, marks every Claude answer again and one in five of the rest, picked by a random draw fixed before marking.
Where they differ
The official source decides. Both marks stay on record.

From run 1 it is GLM-5.2, with Qwen3.7-Max in reserve. It sees the answer, the key and the rules, never a sealed question's wording. If the second read has not run, the answer is published as "second read pending", never as settled.

The graders are AI, and Ben has not checked the grades himself. So every Claude answer is published beside its mark, word for word except any sentence that repeats a sealed question.

Before a grader's marks count, we slip in answers we know are wrong and count the catches. How that test works, and what it found, is its own page: How we check the checker.

No change is called until we know the normal wobble.

Run 1 was a pilot on mixed plans, so it is not part of the baseline. Runs 2 and 3, both on free plans, are the baseline: they show how much the scores move on their own. Run 4 is the first that can call a change, and each run from then on is set against up to four runs before it, never run 1. Each run ends on one of three words: Improved, Slipped or No change detected.

What has to be true before a change is called

Both of these, or nothing is called:

  • The move is bigger than chance would explain (Fisher's exact test, p under 0.05, right against not right).
  • The move is bigger than the swing that app showed between its two baseline runs.

Say an app got 108 of its 120 tries right over four runs. A run at 22 of 30 or below would be called Slipped. From that high, no run could be called Improved, and the report says so.

"No change detected" means no change big enough to see, not "the same". One question flipping is reported, never called a trend on its own.

What a run can show, and what it can't.

It shows

What six AI apps, each on its free plan and signed in, said on the day to ten fixed UK questions, marked by AI graders against keys written before the answers. Run 1, a pilot, ran on mixed plans.

It is not

  • A ranking of the apps
  • How they do on other questions, days or countries
  • A verdict on the models behind the apps
  • Legal advice
Why a change can have more than one cause

A move from one run to the next can come from a model, routing or search change, and the report says so whenever it calls one. Run 1 ran on mixed plans (ChatGPT logged out, Claude and Perplexity paid), so its scores are not set against later runs. From run 2 every app is on its free plan, so the plan is no longer a reason for a move.