gold
SELECT T2.element FROM connected AS T1 INNER JOIN atom AS T2 ON T1.atom_id = T2.atom_id WHERE T1.bond_id = 'TR144_8_19'
this statement states no ordering of its own
sha256:d0f3d53ce7e8b02eacee55dca1782682dde4a27b793e7c1a8b7bd9cf5a25b464
R-SET NOT_EQUAL
toxicology · mini_dev_sqlite from https://bird-bench.oss-cn-beijing.aliyuncs.com/minidev.zip (sha256 cc48ba16838204e4e214512030cb572eeb5f7bcdd999bae4b9b6ff12ec13b92f, downloaded 2026-09-07), member minidev/MINIDEV/mini_dev_sqlite.json
What are the elements of the atoms of TR144_8_19?
the hint the set supplies: TR144_8_19 is the bond id;
NOT_EQUAL states that these two statements disagree on this data under this rule. It does not state which of them is wrong.
SELECT T2.element FROM connected AS T1 INNER JOIN atom AS T2 ON T1.atom_id = T2.atom_id WHERE T1.bond_id = 'TR144_8_19'
this statement states no ordering of its own
sha256:d0f3d53ce7e8b02eacee55dca1782682dde4a27b793e7c1a8b7bd9cf5a25b464
SELECT a.element
FROM connected c
JOIN atom a ON c.atom_id = a.atom_id OR c.atom_id2 = a.atom_id
JOIN bond b ON c.bond_id = b.bond_id
WHERE b.bond_id = 'TR144_8_19';
this statement states no ordering of its own
sha256:1c4262b65afa74cc1f367f13abb9a16e960764c340a59ff7a991bc1fd2526a68
The marked tokens are where the two texts differ. Two statements that differ everywhere can return the same rows, and two that differ in one token can return other rows; the verdict above is read off the results.
from counterexample.json, 0 rows, up to 25 shown per side
| side | elementTEXT |
|---|---|
| no rows |
from counterexample.json, 2 rows, up to 25 shown per side
| side | elementTEXT |
|---|---|
| second | c |
| second | h |
set(second_rows) == set(gold_rows), REAL cells as Python float as sqlite3 returns them, so Python equality holds 1 == 1.0 == True as the benchmark's own scorer does
https://github.com/bird-bench/mini_dev/blob/main/evaluation/evaluation_ex.py
result_eq: equal row counts and equal column counts, each row unordered as a quick rejection, then the two equal as a list when the gold text holds ORDER BY and as a multiset otherwise, under some permutation of the columns; DISTINCT is not stripped and re-executed, and the cells are SQLite's as sqlite3 returns them
ruiqi-zhong/test-suite-sql-eval, exec_eval.py, result_eq, at commit 48cb78ec: https://github.com/ruiqi-zhong/test-suite-sql-eval/blob/48cb78ecf7f610620206283846c76751b18a1326/exec_eval.py
The class states what makes these two results unequal under this rule, read off the two results and nothing else. It does not state which of the two statements is wrong.
from counterexample.json, 2 rows
| elementTEXT |
|---|
| h |
| c |
from counterexample.json, 4 rows
| elementTEXT |
|---|
| h |
| c |
| h |
| c |
A smell is a mechanical reason to read this gold statement again. It is a heuristic: it does not state that the statement is wrong, and a maintainer decides.
this statement orders by a text column holding only numbers, and ordering it as a number gives a different answer, so the gold may be sorting 9.5 above 10
the statement states no top level ORDER BY
{
"heuristic": true,
"reason": "the statement states no top level ORDER BY"
}
this statement cuts its result at a LIMIT that does not decide which rows come back, so a different but equally correct statement can return other rows and score zero
the statement states no LIMIT
{
"heuristic": true,
"reason": "the statement states no LIMIT"
}
rerun over the same rows in another physical order this statement gives another answer, so its result depends on how the rows are stored and not only on the data
{
"heuristic": true,
"rule": "R-SET",
"baseline_result_hash": "sha256:d0f3d53ce7e8b02eacee55dca1782682dde4a27b793e7c1a8b7bd9cf5a25b464",
"baseline_result": {
"columns": [
{
"name": "element",
"declared_type": "TEXT"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "h"
}
],
[
{
"type": "str",
"value": "c"
}
]
],
"result_hash": "sha256:d0f3d53ce7e8b02eacee55dca1782682dde4a27b793e7c1a8b7bd9cf5a25b464"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"connected",
"atom"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:72c2a8b65b1dc21678c752652db3a2555e62afe7cabd461a9ad29d6195660981",
"result": {
"columns": [
{
"name": "element",
"declared_type": "TEXT"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "c"
}
],
[
{
"type": "str",
"value": "h"
}
]
],
"result_hash": "sha256:72c2a8b65b1dc21678c752652db3a2555e62afe7cabd461a9ad29d6195660981"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}
SELECT T2.element FROM connected AS T1 INNER JOIN atom AS T2 ON T1.atom_id = T2.atom_id WHERE T1.bond_id = 'TR144_8_19'
result_hash sha256:d0f3d53ce7e8b02eacee55dca1782682dde4a27b793e7c1a8b7bd9cf5a25b464 recomputed from this JSON: match
record_hash sha256:df46854e1541bfd0b34ef48359123f9601af863c179c0c45d76294d4caabe1f4 recomputed from this JSON: match
from evidence-gold.json, 2 rows
| elementTEXT |
|---|
| h |
| c |
SELECT a.element
FROM connected c
JOIN atom a ON c.atom_id = a.atom_id OR c.atom_id2 = a.atom_id
JOIN bond b ON c.bond_id = b.bond_id
WHERE b.bond_id = 'TR144_8_19';
result_hash sha256:1c4262b65afa74cc1f367f13abb9a16e960764c340a59ff7a991bc1fd2526a68 recomputed from this JSON: match
record_hash sha256:b98c5c09c36121ef5162c4ea1e652013b5881fc49635a73a12cf12f14f17fa2d recomputed from this JSON: match
from evidence-second.json, 4 rows
| elementTEXT |
|---|
| h |
| c |
| h |
| c |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/minidev/dev_databases/toxicology/toxicology.sqlite | size=2678784 under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/minidev/dev_databases/toxicology/toxicology.sqlite | size=2678784 under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET