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 type of bond is there between the atoms TR004_8 and TR004_20?
the hint the set supplies: type of bond refers to bond_type; between the atoms TR004_8 and TR004_20 refers to atom_id = 'TR004_8' AND atom_id2 = 'TR004_20' OR another way around
NOT_EQUAL states that these two statements disagree on this data under this rule. It does not state which of them is wrong.
SELECT T1.bond_type FROM bond AS T1 INNER JOIN connected AS T2 ON T1.bond_id = T2.bond_id WHERE T2.atom_id = 'TR004_8' AND T2.atom_id2 = 'TR004_20' OR T2.atom_id2 = 'TR004_8' AND T2.atom_id = 'TR004_20'this statement states no ordering of its own
sha256:6494225cf2e36d1309907c24ded48b317f07b6777128c8cfda23303c76876a2f
SELECT bond_type FROM bond WHERE molecule_id = (SELECT molecule_id FROM connected WHERE atom_id = 'TR004_8' AND atom_id2 = 'TR004_20') AND bond_id IN (SELECT bond_id FROM connected WHERE atom_id = 'TR004_8' AND atom_id2 = 'TR004_20');this statement states no ordering of its own
sha256:7f7236114242692825e6f800a3f4f05ed41ded9da4e30bfd110072c515a0f7a1
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, 1 row, up to 25 shown per side
| side | bond_typeTEXT |
|---|---|
| gold | - |
from counterexample.json, 0 rows, up to 25 shown per side
| side | bond_typeTEXT |
|---|---|
| no rows |
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
| bond_typeTEXT |
|---|
| - |
| - |
from counterexample.json, 1 row
| bond_typeTEXT |
|---|
| - |
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:6494225cf2e36d1309907c24ded48b317f07b6777128c8cfda23303c76876a2f",
"baseline_result": {
"columns": [
{
"name": "bond_type",
"declared_type": "TEXT"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "-"
}
],
[
{
"type": "str",
"value": "-"
}
]
],
"result_hash": "sha256:6494225cf2e36d1309907c24ded48b317f07b6777128c8cfda23303c76876a2f"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"bond",
"connected"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:6494225cf2e36d1309907c24ded48b317f07b6777128c8cfda23303c76876a2f",
"result": {
"columns": [
{
"name": "bond_type",
"declared_type": "TEXT"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "-"
}
],
[
{
"type": "str",
"value": "-"
}
]
],
"result_hash": "sha256:6494225cf2e36d1309907c24ded48b317f07b6777128c8cfda23303c76876a2f"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT T1.bond_type FROM bond AS T1 INNER JOIN connected AS T2 ON T1.bond_id = T2.bond_id WHERE T2.atom_id = 'TR004_8' AND T2.atom_id2 = 'TR004_20' OR T2.atom_id2 = 'TR004_8' AND T2.atom_id = 'TR004_20'result_hash sha256:6494225cf2e36d1309907c24ded48b317f07b6777128c8cfda23303c76876a2f recomputed from this JSON: match
record_hash sha256:f128109a02e8fc7ed74969a3cba01efa05c4b54965893ad564142f2369d2b0f5 recomputed from this JSON: match
from evidence-gold.json, 2 rows
| bond_typeTEXT |
|---|
| - |
| - |
SELECT bond_type FROM bond WHERE molecule_id = (SELECT molecule_id FROM connected WHERE atom_id = 'TR004_8' AND atom_id2 = 'TR004_20') AND bond_id IN (SELECT bond_id FROM connected WHERE atom_id = 'TR004_8' AND atom_id2 = 'TR004_20');result_hash sha256:7f7236114242692825e6f800a3f4f05ed41ded9da4e30bfd110072c515a0f7a1 recomputed from this JSON: match
record_hash sha256:b2e00e75d6c37769ed9f733fa14aa462df6774a3b7666397170d1c9677211809 recomputed from this JSON: match
from evidence-second.json, 1 row
| bond_typeTEXT |
|---|
| - |
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