q207

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

The question

What elements are in a double type bond?

the hint the set supplies: double type bond refers to bond_type = '=';

NOT_EQUAL states that these two statements disagree on this data under this rule. It does not state which of them is wrong.

The statements

gold

SELECT DISTINCT T1.element FROM atom AS T1 INNER JOIN bond AS T2 ON T1.molecule_id = T2.molecule_id INNER JOIN connected AS T3 ON T1.atom_id = T3.atom_id WHERE T2.bond_type = '='

this statement states no ordering of its own

sha256:86a36104a8d53ec8bd73f49f3d83f044daf88dffa0b84975309b4b0882404937

second

SELECT DISTINCT a.element
FROM atom a
JOIN connected c ON a.atom_id = c.atom_id OR a.atom_id = c.atom_id2
JOIN bond b ON c.bond_id = b.bond_id
WHERE b.bond_type = '='

this statement states no ordering of its own

sha256:49006cdef0aa765e24c0214c97446edad6b7dea49b130b785c47db04326e6eb6

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.

The rows they differ in

in gold, not in the prediction, 8 rows

from counterexample.json, 8 rows, up to 25 shown per side

side elementtext
gold br
gold cl
gold cu
gold f
gold h
gold p
gold pb
gold sn

in the prediction, not in gold, 0 rows

from counterexample.json, 0 rows, up to 25 shown per side

side elementtext
no rows

What the benchmark would have said

BIRD's own check: 0

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

gold_rows
13
second_rows
5
gold_distinct_rows
13
second_distinct_rows
5

the test-suite check: 0

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

order_matters
false
gold_rows
13
second_rows
5
gold_columns
1
second_columns
1

the class: other

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.

gold_types
["text"]
second_types
["text"]
multiset_equal
false
set_equal
false
order_equal
false
shorter_result_is_a_prefix
false

The results

gold, 13 rows

from counterexample.json, 13 rows

elementtext
sn
ca
cu
p
h
cl
o
s
c
br
n
f
pb
second, 5 rows

from counterexample.json, 5 rows

elementtext
ca
o
s
c
n

The probes

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.

ordering-over-numeric-text not applicable

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

what it measured 
{
  "heuristic": true,
  "reason": "the statement states no top level ORDER BY"
}

arbitrary-cut not applicable

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

what it measured 
{
  "heuristic": true,
  "reason": "the statement states no LIMIT"
}

not-a-function-of-the-data quiet

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

what it measured 
{
  "heuristic": true,
  "rule": "R-SET",
  "baseline_result_hash": "sha256:86a36104a8d53ec8bd73f49f3d83f044daf88dffa0b84975309b4b0882404937",
  "baseline_result": {
    "columns": [
      {
        "name": "element",
        "declared_type": "text"
      }
    ],
    "row_count": 13,
    "truncated": false,
    "rows_shown": 10,
    "rows": [
      [
        {
          "type": "str",
          "value": "sn"
        }
      ],
      [
        {
          "type": "str",
          "value": "ca"
        }
      ],
      [
        {
          "type": "str",
          "value": "cu"
        }
      ],
      [
        {
          "type": "str",
          "value": "p"
        }
      ],
      [
        {
          "type": "str",
          "value": "h"
        }
      ],
      [
        {
          "type": "str",
          "value": "cl"
        }
      ],
      [
        {
          "type": "str",
          "value": "o"
        }
      ],
      [
        {
          "type": "str",
          "value": "s"
        }
      ],
      [
        {
          "type": "str",
          "value": "c"
        }
      ],
      [
        {
          "type": "str",
          "value": "br"
        }
      ]
    ],
    "result_hash": "sha256:86a36104a8d53ec8bd73f49f3d83f044daf88dffa0b84975309b4b0882404937"
  },
  "planner_statistics": {
    "connected": {
      "last_analyze": null,
      "last_autoanalyze": "2026-09-08 05:19:17.010277+00",
      "n_mod_since_analyze": 0
    },
    "atom": {
      "last_analyze": null,
      "last_autoanalyze": "2026-09-08 05:19:10.04421+00",
      "n_mod_since_analyze": 0
    },
    "bond": {
      "last_analyze": null,
      "last_autoanalyze": "2026-09-08 05:19:12.802916+00",
      "n_mod_since_analyze": 0
    }
  },
  "shuffle": {
    "seed": "1",
    "row_limit": 300000,
    "tables": [
      "connected",
      "atom",
      "bond"
    ],
    "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:5225012cf01a09444b64a3fddaa2f54cfbbb4168ca13d2e4b5a5e78d603c75c4",
    "result": {
      "columns": [
        {
          "name": "element",
          "declared_type": "text"
        }
      ],
      "row_count": 13,
      "truncated": false,
      "rows_shown": 10,
      "rows": [
        [
          {
            "type": "str",
            "value": "n"
          }
        ],
        [
          {
            "type": "str",
            "value": "ca"
          }
        ],
        [
          {
            "type": "str",
            "value": "br"
          }
        ],
        [
          {
            "type": "str",
            "value": "cu"
          }
        ],
        [
          {
            "type": "str",
            "value": "cl"
          }
        ],
        [
          {
            "type": "str",
            "value": "c"
          }
        ],
        [
          {
            "type": "str",
            "value": "pb"
          }
        ],
        [
          {
            "type": "str",
            "value": "h"
          }
        ],
        [
          {
            "type": "str",
            "value": "o"
          }
        ],
        [
          {
            "type": "str",
            "value": "s"
          }
        ]
      ],
      "result_hash": "sha256:5225012cf01a09444b64a3fddaa2f54cfbbb4168ca13d2e4b5a5e78d603c75c4"
    }
  },
  "plan_variant": {
    "run": false,
    "reason": "the plan variant was not asked for"
  }
}

The evidence records

gold: evidence-gold.json

SELECT DISTINCT T1.element FROM atom AS T1 INNER JOIN bond AS T2 ON T1.molecule_id = T2.molecule_id INNER JOIN connected AS T3 ON T1.atom_id = T3.atom_id WHERE T2.bond_type = '='
statement read from
data/questions/mini_dev_postgresql.json
digest
sha256:d2731292f20b8d8569cd956dd747ffe1df13cd625076263e38ae9ebcef50b1ab
origin
https://bird-bench.oss-cn-beijing.aliyuncs.com/minidev.zip (sha256 cc48ba16838204e4e214512030cb572eeb5f7bcdd999bae4b9b6ff12ec13b92f, downloaded 2026-09-07), member minidev/MINIDEV/mini_dev_postgresql.json, 2024-06-19

result_hash sha256:86a36104a8d53ec8bd73f49f3d83f044daf88dffa0b84975309b4b0882404937 recomputed from this JSON: match

record_hash sha256:85fce2f618aa337a0e54099bf370a0e50ac2a4a71c8feb5ea355bf9aa2047dc9 recomputed from this JSON: match

the result this record holds, 13 rows

from evidence-gold.json, 13 rows

elementtext
sn
ca
cu
p
h
cl
o
s
c
br
n
f
pb
what ran, and where
run
audit-34520748-ce64-4674-9cd7-6d6fac5b9805
executed at
2026-09-08T05:24:05.678463+00:00
data as of
2026-09-08T05:23:23.924963+00:00
backend at checkout
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
backend that answered
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
database role
auditor
replay rule
R-SET
question set version
sha256:d2731292f20b8d8569cd956dd747ffe1df13cd625076263e38ae9ebcef50b1ab
validator
audit:libpg_query-parse
checks run
parses_as_exactly_one_statement, the_one_statement_is_a_select, no_placeholder_without_a_bound_parameter
statement timeout
120000 ms
rows
13 rows
the session it ran under
engine
postgresql
time_zone
Etc/UTC
date_style
ISO, MDY
interval_style
postgres
extra_float_digits
1
database_collation
en_US.utf8
work_mem
4096
hash_mem_multiplier
2

recorded beside them

statement_timeout
0
search_path
"$user", public
server_version
16.15 (Debian 16.15-1.pgdg13+2)
server_version_num
160015
transaction_read_only
on
max_parallel_workers_per_gather
2
server_encoding
UTF8
datlocprovider
c
daticulocale
datcollversion
2.41
the rendering and the data
version
attestql/audit/2
numeric_scale
6
timestamp_format
%Y-%m-%dT%H:%M:%S.%fZ
timezone
UTC
null_rendering
NULL
encoding
utf-8
schema digest
sha256:ee9efd06befc46a5577044a8a367673c5fba8bc2c66e5b735e68ab585b369194
source file sha256
sha256:31b1da211849d24a57c9af7636da46a5b82fc8a3ca1542bb3ebd8775e9a31cec
rows in public.atom
9111
rows in public.bond
9156
rows in public.connected
18312

second: evidence-second.json

SELECT DISTINCT a.element
FROM atom a
JOIN connected c ON a.atom_id = c.atom_id OR a.atom_id = c.atom_id2
JOIN bond b ON c.bond_id = b.bond_id
WHERE b.bond_type = '='
statement read from
data/preds-pg/predict_mini_dev_gpt-4_postgresql.json
digest
sha256:cd39466740516d2d4672e8421010edab4816ff9875781f44df100840b41eaa49
origin
https://raw.githubusercontent.com/bird-bench/mini_dev/b3d4bcbbae9a96934ad812551eb400c7a3b23c12/llm/exp_result/sql_output_kg/predict_mini_dev_gpt-4_postgresql.json, 2024-06-19

result_hash sha256:49006cdef0aa765e24c0214c97446edad6b7dea49b130b785c47db04326e6eb6 recomputed from this JSON: match

record_hash sha256:b21148bcc42bedd64155d8091e168d2c20c0f7b576fef77f8acbafb8a14048af recomputed from this JSON: match

the result this record holds, 5 rows

from evidence-second.json, 5 rows

elementtext
ca
o
s
c
n
what ran, and where
run
audit-34520748-ce64-4674-9cd7-6d6fac5b9805
executed at
2026-09-08T05:24:05.692022+00:00
data as of
2026-09-08T05:23:23.924963+00:00
backend at checkout
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
backend that answered
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
database role
auditor
replay rule
R-SET
question set version
sha256:d2731292f20b8d8569cd956dd747ffe1df13cd625076263e38ae9ebcef50b1ab
validator
audit:libpg_query-parse
checks run
parses_as_exactly_one_statement, the_one_statement_is_a_select, no_placeholder_without_a_bound_parameter
statement timeout
120000 ms
rows
5 rows
the session it ran under
engine
postgresql
time_zone
Etc/UTC
date_style
ISO, MDY
interval_style
postgres
extra_float_digits
1
database_collation
en_US.utf8
work_mem
4096
hash_mem_multiplier
2

recorded beside them

statement_timeout
0
search_path
"$user", public
server_version
16.15 (Debian 16.15-1.pgdg13+2)
server_version_num
160015
transaction_read_only
on
max_parallel_workers_per_gather
2
server_encoding
UTF8
datlocprovider
c
daticulocale
datcollversion
2.41
the rendering and the data
version
attestql/audit/2
numeric_scale
6
timestamp_format
%Y-%m-%dT%H:%M:%S.%fZ
timezone
UTC
null_rendering
NULL
encoding
utf-8
schema digest
sha256:ee9efd06befc46a5577044a8a367673c5fba8bc2c66e5b735e68ab585b369194
source file sha256
sha256:31b1da211849d24a57c9af7636da46a5b82fc8a3ca1542bb3ebd8775e9a31cec
rows in public.atom
9111
rows in public.bond
9156
rows in public.connected
18312

Running these again

gold

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

second

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

This question's run

run
audit-34520748-ce64-4674-9cd7-6d6fac5b9805
server
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
question set
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
replay rule
R-SET

the run this question belongs to

The JSON this page was rendered from