R-SET NOT_EQUAL
toxicology · mini_dev_postgresql from https://bird-bench.oss-cn-beijing.aliyuncs.com/minidev.zip (sha256 cc48ba16838204e4e214512030cb572eeb5f7bcdd999bae4b9b6ff12ec13b92f, downloaded 2026-09-07), member minidev/MINIDEV/mini_dev_postgresql.json
What elements are in the TR004_8_9 bond atoms?
the hint the set supplies: TR004_8_9 bond atoms refers to bond_id = 'TR004_8_9';
NOT_EQUAL states that these two statements disagree on this data under this rule. It does not state which of them is wrong.
read by hand, 2026-09-04: B harmless: one distinct row repeated; DISTINCT added by the prediction; a list under twice the answer with every row present
one distinct row (c) repeated
a maintainer's reading of this question, out of classification.json, copied from plans/reports/prediction-mode-260904-real-predictions/classification.json. It is not a verdict and nothing above it was computed from it.
SELECT DISTINCT T1.element FROM atom AS T1 INNER JOIN connected AS T2 ON T1.atom_id = T2.atom_id WHERE T2.bond_id = 'TR004_8_9'this statement states no ordering of its own
sha256:b44616029adcfdf6d39a7bb78fccdab3dcac6397ba94695654c9f003989fef8d
SELECT a.element
FROM atom a
JOIN connected c ON a.atom_id = c.atom_id
JOIN bond b ON c.bond_id = b.bond_id
WHERE b.bond_id = 'TR004_8_9';this statement states no ordering of its own
sha256:de447c9a13cbce318e97c9c5bf155240a9101328fd3a6c92db499675ec9436dc
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, 1 row, up to 25 shown per side
| side | elementtext |
|---|---|
| second | c |
set(second_rows) == set(gold_rows), float4/float8 cells as Python float as psycopg2 returns them, numeric as Decimal
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 PostgreSQL's as psycopg2 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, 1 row
| elementtext |
|---|
| c |
from counterexample.json, 2 rows
| elementtext |
|---|
| c |
| 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:b44616029adcfdf6d39a7bb78fccdab3dcac6397ba94695654c9f003989fef8d",
"baseline_result": {
"columns": [
{
"name": "element",
"declared_type": "text"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "c"
}
]
],
"result_hash": "sha256:b44616029adcfdf6d39a7bb78fccdab3dcac6397ba94695654c9f003989fef8d"
},
"planner_statistics": {
"atom": {
"last_analyze": null,
"last_autoanalyze": "2026-09-08 05:19:10.04421+00",
"n_mod_since_analyze": 0
},
"connected": {
"last_analyze": null,
"last_autoanalyze": "2026-09-08 05:19:17.010277+00",
"n_mod_since_analyze": 0
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"atom",
"connected"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {
"laptimes": 400524,
"legalities": 427907,
"posthistory": 303155,
"trans": 1056320,
"yearmonth": 383282
},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:b44616029adcfdf6d39a7bb78fccdab3dcac6397ba94695654c9f003989fef8d",
"result": {
"columns": [
{
"name": "element",
"declared_type": "text"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "c"
}
]
],
"result_hash": "sha256:b44616029adcfdf6d39a7bb78fccdab3dcac6397ba94695654c9f003989fef8d"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT DISTINCT T1.element FROM atom AS T1 INNER JOIN connected AS T2 ON T1.atom_id = T2.atom_id WHERE T2.bond_id = 'TR004_8_9'result_hash sha256:b44616029adcfdf6d39a7bb78fccdab3dcac6397ba94695654c9f003989fef8d recomputed from this JSON: match
record_hash sha256:78853ba210da0d87ba3053dffef5eff776e7e774b836f2f97726cf405f79a086 recomputed from this JSON: match
from evidence-gold.json, 1 row
| elementtext |
|---|
| c |
SELECT a.element
FROM atom a
JOIN connected c ON a.atom_id = c.atom_id
JOIN bond b ON c.bond_id = b.bond_id
WHERE b.bond_id = 'TR004_8_9';result_hash sha256:de447c9a13cbce318e97c9c5bf155240a9101328fd3a6c92db499675ec9436dc recomputed from this JSON: match
record_hash sha256:3cabf60e07d603080a346d9708c2d17a521d685c65a6bc9103fef6f16f1a7238 recomputed from this JSON: match
from evidence-second.json, 2 rows
| elementtext |
|---|
| c |
| c |
re-run this statement read-only against PostgreSQL 16.15 (Debian 16.15-1.pgdg13+2) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit | server=172.17.0.2/32:5432 | database=bird 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 PostgreSQL 16.15 (Debian 16.15-1.pgdg13+2) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit | server=172.17.0.2/32:5432 | database=bird under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET