Basedash in AI Database Agents
Scenario-level performance from current published Results.
12 of 28 scenarios published
Where Basedash failed
1 of 12 graded scenarios. Open a Result to see the conversation and the evidence.
The agent offers what to ask next
Basedash did not offer a follow-up question after answering in web chat. It answered the revenue question but left the space below the answer empty, even after eight minutes.
View Result →How Basedash performed
Open a capability to explore its scenarios. Each row reports the test set in its published Result.
Analytics & Observability1 pass3 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A user reports a bad answer and the operator has to find it | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedBasedash made the complained-about exchange findable and inspectable. The chat list led to the question and full answer, and also opened two chats from another member. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Reported analytics match what actually happened | No published result | ||
| Someone needs to see what people have been asking | No published result | ||
| The operator needs to find the questions the agent is failing on | No published result | ||
Answer Presentation4 pass
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The answer is a plain fact or a short list | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedBasedash handled the single-value presentation scenario correctly. It answered with 308 in prose, the one-row result panel supported that answer rather than replacing it, and no chart appeared. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The answer is a trend or a comparison | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedBasedash showed the monthly order trend as both a table and an unasked bar chart. The bars rose from June to August, and the answer used the three completed calendar months in Asia/Calcutta. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The answer needs a summary and its detail together | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedBasedash passes this presentation case. It gave a headline figure, a month-comparison table, and a separate category breakdown whose contributions add to the stated change. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The user asks to see the same answer a different way | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedBasedash turned its revenue tables into a stacked bar chart on request without changing the figures. The chart retained July’s $10,953.75 total, August’s $8,847.45 total and all fourteen category figures from the earlier answer. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Conversational Interaction2 pass1 fail3 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Customer corrects information given earlier | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedBasedash used the customer’s correction and returned the database’s June 2026 total of 11 orders. It answered for June alone, rather than keeping July’s answer or combining the months. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The agent offers what to ask next | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedBasedash did not offer a follow-up question after answering in web chat. It answered the revenue question but left the space below the answer empty, even after eight minutes. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The next question refers to the previous answer | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedBasedash kept the previous answer’s set in a follow-up question. It counted 86 orders for the same five customers without asking who they were. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The follow-up is ambiguous | No published result | ||
| The user changes direction mid-conversation | No published result | ||
| The user narrows what they just asked | No published result | ||
Question Answering2 pass2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The connected data cannot answer the question | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedBasedash declined to give a count of 5-star reviews for October 2026 from the connected data. It described the count as unavailable rather than zero. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The user's wording doesn't match how the values are stored | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedBasedash understood the gift-voucher request and returned all 14 matching orders. Their total was USD 16,806.08, the stated reference total, and two were cancelled. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The answer is available in the connected data | No published result | ||
| The question uses a term the company defines itself | No published result | ||
Reporting2 pass1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The report is run again after the data has changed | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedBasedash preserved the requested period when the saved report was refreshed after data changed. The order count rose from 23 to 26, the new reference count. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The user wants several findings in one place | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedBasedash passed this scenario. One chat shows three separate answers and a fourth report that repeats the same figures: August revenue $8,795.45, a bedding and rugs/home decor tie at 106 units each, Furniture at $51,248.25, and a 21.75% cancellation rate. Its verification query returned the same values. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The user wants to keep an answer they just got | No published result | ||
Data Access Control3 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| An excluded column is asked for directly | No published result | ||
| An excluded table is needed to answer the question | No published result | ||
| Two users are given different data scope | No published result | ||
Training4 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The agent used the wrong definition and the user corrects it | No published result | ||
| The database's names are cryptic and the user documents them | No published result | ||
| The user sets a standing rule for all future answers | No published result | ||
| The user supplies example questions and the queries they trust | No published result | ||
Reading these Results
Published evidence and test coverage answer different questions.
Which scenarios have a Result?
A published Result is public evidence for this tool on one scenario. “No published result” does not say whether testing has taken place.
What does each Result cover?
Assessed includes Pass, Fail and Not gradable. Gradable includes Pass and Fail. Both use the pinned test count in that published Result.
Out of 28 scenarios
The summary counts each of the 28 scenarios once. A scenario fails when any of its published test cases failed. “No published Result yet” means nothing is public for that scenario; it does not say whether Basedash was tested on it.