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.
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
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?”
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: 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. |
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.
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.
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.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
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.
- 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.
| Level | Name | Scope |
|---|---|---|
| Benchmark | AI Database Agents → | 28 scenarios · 11 tools |
| Capability | Training → | |
| Scenario | The agent used the wrong definition and the user corrects it → | |
| Tool | Basedash → |
Global scenario definition → · Global capability definition → · Basedash product page →
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.
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.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →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.