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

Does Basedash ask for clarification when a follow-up is ambiguous?

Basedash chose an interpretation of an ambiguous follow-up without asking for clarification. It combined the two top-three customer groups into a five-row comparison table with explanatory bullets.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
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.

"Compare them" with two candidate setsFailEvidence
What we sent

Input 1 · Initial comparison request: “Compare our top 3 customers by order count against our top 3 customers by total spend.”

Input 2 · Ambiguous follow-up: “Compare them.”

What the tool returned

Initial answer: two customer groups

Only Jae-won Park appears in both top-three lists. Wei Zhang leads by order count, while Dev Raghavan leads by total spend. Top 3 by order count Rank | Customer | Orders | Total spend | Spend rank 1 | Wei Zhang | 26 | $17,875.23 | 5 2 | Jae-won Park | 24 | $19,007.14 | 3 3 | Rosa Delgado | 24 | $18,210.72 | 4 Top 3 by total spend Rank | Customer | Total spend | Orders | Order-count rank 1 | Dev Raghavan | $24,210.69 | 22 | 5 2 | Priya Raghavan | $21,597.62 | 23 | 4 3 | Jae-won Park | $19,007.14 | 24 | 2 The highest-spending customers place fewer orders than the order-count leader, indicating larger average order values. Scope: all recorded orders, including cancelled orders. Spend is the sum of order totals, without subtracting refunds. Order-count ties are broken by total spend, placing Jae-won ahead of Rosa.

Answer to the ambiguous follow-up

Only Jae-won Park appears in both top-three lists. Wei Zhang leads by order count, while Dev Raghavan leads by total spend. Customer | Orders | Order-count rank | Total spend | Spend rank Wei Zhang | 26 | 1 | $17,875.23 | 5 Jae-won Park | 24 | 2 | $19,007.14 | 3 Rosa Delgado | 24 | 3 | $18,210.72 | 4 Priya Raghavan | 23 | 4 | $21,597.62 | 2 Dev Raghavan | 22 | 5 | $24,210.69 | 1 Order-count top three: Wei, Jae-won, and Rosa. Spend top three: Dev, Priya, and Jae-won. Key difference: Dev and Priya spend more despite placing fewer orders than any customer in the order-count top three. Based on all recorded orders, including cancelled orders. Spend sums order totals without subtracting refunds. The 24-order tie between Jae-won and Rosa is broken by total spend.

Transcribed from Proof 1 · Screen recording at 0:12

Every message the tool sent, in order (2)
  1. Initial answer: two customer groups

    Printed above.

  2. Answer to the ambiguous follow-up

    The final response, printed above.

Expected vs. Found
✗Expected: Ask which group is meant rather than silently choosing an interpretation.Found: It answered immediately, with no clarifying question and no additional analysis step or database query.
Supporting proof
Proof 1Screen recording
Screen recording: both customer rankings and the follow-up answered without clarification
Key moments
Open original ↗
Why this result

The first answer left two plausible groups to compare, so clarification was required. The follow-up reached Basedash and received a full answer without a question.

Also observed in this test case

Initial ranking scope and ties. The initial ranking answer included cancelled orders in its stated scope and used total spend to break the 24-order tie.

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
The first answer needed two different customer groups that the follow-up could equally plausibly refer to: the top three by order count and the top three by total spend.
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.

LevelNameScope
BenchmarkAI Database Agents →28 scenarios · 11 tools
CapabilityConversational Interaction →
ScenarioThe follow-up is ambiguous →
ToolBasedash →

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
16 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/the-follow-up-is-ambiguous · 0 pass · 1 fail · coverage 1/1 · graded 2026-11-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 recording634c1c78e9bb06920b3c97db5859da1a217d1dc68bd26b20a1e3d4f223a47956