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

Does Basedash use a user's corrected definition on follow-up and rephrased questions?

Basedash applied the revenue correction saved in its AI context to both the repeated question and a reworded one, each asked in a new chat. Both returned $23,469.02 across 42 non-cancelled orders, the total with cancelled orders left out, against $39,806.75 across 57 orders if they were counted.

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

Correction added to Basedash's organization-wide AI context: 'Our revenue definition excludes cancelled orders - please use that going forward.'

Input 1 · Repeated question, new chat: “As of September 2, 2026, what was our total revenue over the last 90 days?”

Input 2 · Reworded question, new chat: “As of September 2, 2026, how much did we earn in total over the last 90 days?”

What the tool returned

Answer to the repeated question Total revenue was $23,469.02 for the 90 days ending September 2, 2026 (June 5-September 2, inclusive), across 42 non-cancelled orders. / This sums order totals and excludes orders currently marked cancelled, per your revenue definition. It does not reconstruct cancellation status as it stood on September 2. Answer to the reworded question You earned $23,469.02 in total revenue across 42 non-cancelled orders in the 90 days ending September 2, 2026. / This covers June 5-September 2, inclusive, using your Asia/Calcutta time zone. Revenue is the sum of order totals, excluding cancelled orders-not profit.

Transcribed from Proof 1 · Screen recording at 0:06

Transcribed from Proof 1 · Screen recording at 0:14

Expected vs. Found
✓Expected: Both the repeated and the reworded question use the corrected revenue definition and match the reference answer.Found: Both questions returned $23,469.02 across 42 non-cancelled orders, the rule-applied reference ($39,806.75 across 57 orders if the rule is ignored); the second chat's query excluded cancelled orders.
Supporting proof
Proof 1Screen recording
Screen recording: the AI context correction, then both chats with their answers and queries
Key moments
Open original ↗
Why this result

The test needs the corrected definition on a repeat and on a rewording. Both answers gave the rule-applied total and the second chat's query excluded cancelled orders. Since the answer before the correction already left out cancelled orders, this shows the rule holding, not an answer changing.

Also observed in this test case

Two time zones, same totals. The first answer worked in UTC and the second in the Asia/Calcutta time zone; both covered the same window and gave the same totals because no order falls on either boundary.

Current cancellation status used. The first answer said it judges cancellation by each order's current status, not its status on 2 September; that makes no difference to this figure.

Tested by Ayush Ghosh · evidence dated 13 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
Basedash
Build or version
Not exposed by the hosted product
Plan or tier
Free trial
Surface
Web app
Set up before the run
Basedash first answered the revenue question with no correction in place, and that answer already left out cancelled orders. The correction above was then added to the AI context, and the repeated and reworded questions were each asked in a new chat.
AI context
Our revenue definition excludes cancelled orders - please use that going forward.
Tested
13 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
19 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/basedash/definition-correction · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-13

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.

File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screen recording18b45096626d09a0bbe95fdf1792bd1710115aead2defaf3b0f6df847ff33bc4