AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 17 October 2026

Does AskYourDatabase keep a corrected definition when the question is reworded?

AskYourDatabase kept the corrected definition on both the repeated and reworded questions. Each later answer gave the reference revenue total of $23,322.52, compared with $23,597.02 before training.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

The test case

Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.

Corrected metric definition survives a rephrasingPassEvidence
What we sent

A new chat was opened before training.

Input 1 · Before the rule was saved: “As of September 2, 2026, what was our total revenue over the last 90 days?”

Before each of Inputs 2–3: The rule “Our revenue definition excludes cancelled orders and refunded orders.” was saved in the Documentation box, and a new chat was opened.

Input 2 · After the rule was saved: repeated question: “As of September 2, 2026, what was our total revenue over the last 90 days?”

Input 3 · After the rule was saved: rephrased question: “As of September 2, 2026, how much did we earn in total over the last 90 days?”

What the tool returned

Answer before training

As of September 2, 2026, your total revenue over the last 90 days (June 4 – September 2, 2026) was $23,597.02, across 43 orders (excluding cancelled orders).

Answer to the repeated question

As of September 2, 2026, our total revenue over the last 90 days was $23,322.52. This figure excludes cancelled orders and refunded orders, per our revenue definition.

Answer to the rephrased question

As of September 2, 2026, we earned a total of $23,322.52 over the last 90 days. This excludes cancelled and refunded orders, per our revenue definition.

Transcribed from Proof 3 · Screenshot

Every message the tool sent, in order (8)
  1. Progress before training

    I'll calculate the total revenue over the 90 days leading up to September 2, 2026.

  2. SQL before training · not part of the answer
    SELECT SUM(total_amount) AS total_revenue, COUNT(*) AS order_count
    FROM orders
    WHERE placed_at >= '2026-09-02'::timestamp - INTERVAL '90 days'
      AND placed_at < '2026-09-02'::timestamp
      AND status <> 'cancelled'
  3. Answer before training

    Printed above.

  4. Progress after the rule was saved

    I'll calculate the total revenue over the 90 days before September 2, 2026, excluding cancelled and refunded orders per your revenue definition.

  5. SQL for the repeated question · not part of the answer
    SELECT SUM(total_amount) AS total_revenue
    FROM orders
    WHERE placed_at >= '2026-09-02'::timestamp - INTERVAL '90 days'
      AND placed_at < '2026-09-02'::timestamp
      AND status NOT IN ('cancelled')
      AND refunded_at IS NULL;
  6. Answer to the repeated question

    Printed above.

  7. SQL for the rephrased question · not part of the answer
    SELECT SUM(total_amount) AS total_revenue
    FROM orders
    WHERE placed_at >= '2026-09-02'::timestamp - INTERVAL '90 days'
      AND placed_at < '2026-09-02'::timestamp
      AND status NOT IN ('cancelled')
      AND refunded_at IS NULL;
  8. Answer to the rephrased question

    The final response, printed above.

Expected vs. Found
✓Expected: Both the repeated and reworded questions should exclude cancelled and refunded orders and return the reference total of $23,322.52.Found: Both returned $23,322.52, equal to the $23,322.52 reference total; their generated queries excluded cancelled and refunded orders.
Supporting proof
Proof 1Screenshot
Chat screenshot: the revenue question, query and answer before training
Open original ↗
Proof 2Screenshot
Chat screenshot: the repeated question, query and answer after training
Open original ↗
Proof 3Screenshot
Chat screenshot: the reworded question, query and answer after training
Open original ↗
Proof 4Screenshot
Settings screenshot: the revenue rule entered in Documentation
Open original ↗
Why this result

The correction needed to survive both a repeat and a rewording. Both questions were asked in new chats without restating the rule, and the generated queries—not just the answers’ wording—used the corrected exclusions.

Also observed in this test case

Definitions stated in answers. The answer before training described excluding cancelled orders; the repeated and reworded answers also named refunded orders as excluded.

Period wording discrepancy. The answer before training included September 2, 2026 in its stated period, although the query excluded that day. No orders fell on the boundary days, so the total was unaffected.

Tested by Ayush Ghosh · evidence dated 7 October 2026

Configuration and setup

How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.

Software that produced the output
AskYourDatabase
Build or version
Not exposed by the hosted product
Surface
Web app
Set up before the run
Input 1: before training, revenue included refunded orders. The rule excluding cancelled and refunded orders was then saved in Documentation. Inputs 2 and 3: after training, each in a new chat.
Documentation
Our revenue definition excludes cancelled orders and refunded orders.
Tested
7 October 2026 · Ayush Ghosh

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.

The rules
  • Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
  • Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
  • Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.

Where this sits in the benchmark

This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.

History of this result

What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.

from the publication record
13 November 2026First publishedAI Database Agents v1

Act on this result

Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/ai-database-agents/results/askyourdatabase/definition-correction · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-17

The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.

Verify the proof files

These files support this result. Open a file to inspect the original evidence.

Proof 1 · Screenshot ↗image/png · 47 KB
Proof 2 · Screenshot ↗image/png · 43 KB
Proof 3 · Screenshot ↗image/png · 40 KB
Proof 4 · Screenshot ↗image/png · 18 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screenshotf7e12690f3440a94d6f516637d33953d2f3a2f9fe93580cd08f28127a5256595
Proof 2 · Screenshote46b5455ec85caae292a44fc43159a3f094113a8c4e7edb48458c1f1c029c08c
Proof 3 · Screenshot978bd58b907e455c64209e84760af02ef717a492e5bdb036dd1a1e74a27ed0ed
Proof 4 · Screenshotdf2eb610624b0b3a5638093b28589bca7afa7ce536b70bbb3ca16463b1aa7d52