q230

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 are the elements of the toxicology and label of molecule TR060?

the hint the set supplies: TR060 is the molecule id;

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: A a wrong answer the benchmark credited: another table or projection; a scalar repeated per row of an unrelated table; a list at least twice the answer's length where the question asks for the things, not the rows

gold DISTINCT over 5 (element, label) rows; the prediction returns 103

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.

The statements

gold

SELECT DISTINCT T1.element, T2.label FROM atom AS T1 INNER JOIN molecule AS T2 ON T1.molecule_id = T2.molecule_id WHERE T2.molecule_id = 'TR060'

this statement states no ordering of its own

sha256:e2b209c89259c5d16550ab017be6114be2892ac8b55c9fd9aaaa0610ac0f44fd

second

SELECT a.element, m.label
FROM atom a
JOIN molecule m ON a.molecule_id = m.molecule_id
WHERE m.molecule_id = 'TR060';

this statement states no ordering of its own

sha256:f437e1e7839d9b550edcd200d9d04c4deac9f4bb381f0f3e686d9070801c2ffd

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, 0 rows

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

side elementtext labeltext
no rows

in the prediction, not in gold, 98 rows

from counterexample.json, 98 rows, up to 25 shown per side, 4 on this page

sidetimes elementtext labeltext
second58 h -
second38 c -
second1 cl -
second1 o -

What the benchmark would have said

BIRD's own check: 1

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
5
second_rows
103
gold_distinct_rows
5
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
5
second_rows
103
gold_columns
2
second_columns
2

the class: multiplicity

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.

how many rows each result holds, and how many rows both hold, from evidence-gold.json and evidence-second.json5 gold103 prediction5 rows both results hold
The gold returned 5 rows and the prediction 103. 5 rows occur in both results at least once.
gold_types
["text", "text"]
second_types
["text", "text"]
multiset_equal
false
set_equal
true
order_equal
false
shorter_result_is_a_prefix
false

The results

gold, 5 rows

from counterexample.json, 5 rows

elementtext labeltext
o -
cl -
n -
h -
c -
second, 103 rows

from counterexample.json, 103 rows, 25 on this page

elementtext labeltext
c -
c -
h -
h -
h -
h -
c -
c -
c -
c -
c -
c -
o -
c -
c -
c -
c -
c -
c -
c -
o -
c -
c -
c -
c -

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:e2b209c89259c5d16550ab017be6114be2892ac8b55c9fd9aaaa0610ac0f44fd",
  "baseline_result": {
    "columns": [
      {
        "name": "element",
        "declared_type": "text"
      },
      {
        "name": "label",
        "declared_type": "text"
      }
    ],
    "row_count": 5,
    "truncated": false,
    "rows_shown": 5,
    "rows": [
      [
        {
          "type": "str",
          "value": "o"
        },
        {
          "type": "str",
          "value": "-"
        }
      ],
      [
        {
          "type": "str",
          "value": "cl"
        },
        {
          "type": "str",
          "value": "-"
        }
      ],
      [
        {
          "type": "str",
          "value": "n"
        },
        {
          "type": "str",
          "value": "-"
        }
      ],
      [
        {
          "type": "str",
          "value": "h"
        },
        {
          "type": "str",
          "value": "-"
        }
      ],
      [
        {
          "type": "str",
          "value": "c"
        },
        {
          "type": "str",
          "value": "-"
        }
      ]
    ],
    "result_hash": "sha256:e2b209c89259c5d16550ab017be6114be2892ac8b55c9fd9aaaa0610ac0f44fd"
  },
  "planner_statistics": {
    "atom": {
      "last_analyze": "2026-09-14 12:50:57.967668+00",
      "last_autoanalyze": null,
      "n_mod_since_analyze": 0
    },
    "molecule": {
      "last_analyze": "2026-09-14 12:51:03.86612+00",
      "last_autoanalyze": null,
      "n_mod_since_analyze": 0
    }
  },
  "shuffle": {
    "seed": "1",
    "row_limit": 300000,
    "tables": [
      "atom",
      "molecule"
    ],
    "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:7be4ee5f0d749f8a3697eeb1bc5b9d9ee4c55497e7732c2b7ebf1b22381d23fc",
    "result": {
      "columns": [
        {
          "name": "element",
          "declared_type": "text"
        },
        {
          "name": "label",
          "declared_type": "text"
        }
      ],
      "row_count": 5,
      "truncated": false,
      "rows_shown": 5,
      "rows": [
        [
          {
            "type": "str",
            "value": "n"
          },
          {
            "type": "str",
            "value": "-"
          }
        ],
        [
          {
            "type": "str",
            "value": "cl"
          },
          {
            "type": "str",
            "value": "-"
          }
        ],
        [
          {
            "type": "str",
            "value": "h"
          },
          {
            "type": "str",
            "value": "-"
          }
        ],
        [
          {
            "type": "str",
            "value": "o"
          },
          {
            "type": "str",
            "value": "-"
          }
        ],
        [
          {
            "type": "str",
            "value": "c"
          },
          {
            "type": "str",
            "value": "-"
          }
        ]
      ],
      "result_hash": "sha256:7be4ee5f0d749f8a3697eeb1bc5b9d9ee4c55497e7732c2b7ebf1b22381d23fc"
    }
  },
  "plan_variant": {
    "run": false,
    "reason": "the plan variant was not asked for"
  }
}

duplicate-full-row not applicable

this statement returns the same whole row more than once and never says DISTINCT, so a statement answering the same question once per row disagrees on multiplicity alone

what it measured 
{
  "heuristic": true,
  "rows": 5,
  "distinct_rows": 5,
  "repeated_rows": 0,
  "largest_repeat": 1,
  "result_bounded": false,
  "distinct_stated": true,
  "set_operation": false,
  "not_applicable": "the statement states DISTINCT, so it cannot repeat a row"
}

The evidence records

gold: evidence-gold.json

SELECT DISTINCT T1.element, T2.label FROM atom AS T1 INNER JOIN molecule AS T2 ON T1.molecule_id = T2.molecule_id WHERE T2.molecule_id = 'TR060'
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:e2b209c89259c5d16550ab017be6114be2892ac8b55c9fd9aaaa0610ac0f44fd recomputed from this JSON: match

record_hash sha256:e71c3a904c9f36d92a4b9de822760b6e5cd5e8935a7285dcb96ffdd505cd77ed recomputed from this JSON: match

the result this record holds, 5 rows

from evidence-gold.json, 5 rows

elementtext labeltext
o -
cl -
n -
h -
c -
what ran, and where
run
audit-3d090a82-ceab-4c3d-bb4c-19e9c7a03d3b
executed at
2026-09-14T12:55:55.801777+00:00
data as of
2026-09-14T12:55:37.302221+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
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
search_path
public
datlocprovider
c
daticulocale
datcollversion
2.41
the rendering and the data
version
attestql/audit/4
numeric_scale
6
timestamp_format
%Y-%m-%dT%H:%M:%S.%fZ
timezone
UTC
null_rendering
NULL
encoding
utf-8
schema digest
sha256:33a99e27e3c7178b506b333830e16c94682803eccf44c54051b6af0183e0ede3
source file sha256
sha256:31b1da211849d24a57c9af7636da46a5b82fc8a3ca1542bb3ebd8775e9a31cec
rows in public.atom
9111
rows in public.molecule
343

second: evidence-second.json

SELECT a.element, m.label
FROM atom a
JOIN molecule m ON a.molecule_id = m.molecule_id
WHERE m.molecule_id = 'TR060';
statement read from
data/preds-pg/predict_mini_dev_mistralai-mixtral-8x7b-instru-4_postgresql.json
digest
sha256:862dffc4cdca4875650841a456b698e515e978125f5b28f798022e88176562cb
origin
https://raw.githubusercontent.com/bird-bench/mini_dev/b3d4bcbbae9a96934ad812551eb400c7a3b23c12/llm/exp_result/sql_output_kg/predict_mini_dev_mistralai-mixtral-8x7b-instru-4_postgresql.json, 2024-06-19

result_hash sha256:f437e1e7839d9b550edcd200d9d04c4deac9f4bb381f0f3e686d9070801c2ffd recomputed from this JSON: match

record_hash sha256:67de66bed50d926bd5f35cce4eddd359f3d8d2cca429eb2b4f7515414fa74055 recomputed from this JSON: match

the result this record holds, 103 rows, 50 of them here

from evidence-second.json, 103 rows, 50 on this page

elementtext labeltext
c -
c -
h -
h -
h -
h -
c -
c -
c -
c -
c -
c -
o -
c -
c -
c -
c -
c -
c -
c -
o -
c -
c -
c -
c -
c -
c -
c -
c -
c -
c -
c -
c -
c -
c -
n -
c -
c -
c -
c -
c -
cl -
cl -
h -
h -
h -
h -
h -
c -
h -

The whole result is in evidence-second.json, beside this page.

what ran, and where
run
audit-3d090a82-ceab-4c3d-bb4c-19e9c7a03d3b
executed at
2026-09-14T12:55:55.806137+00:00
data as of
2026-09-14T12:55:37.302221+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
103 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
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
search_path
public
datlocprovider
c
daticulocale
datcollversion
2.41
the rendering and the data
version
attestql/audit/4
numeric_scale
6
timestamp_format
%Y-%m-%dT%H:%M:%S.%fZ
timezone
UTC
null_rendering
NULL
encoding
utf-8
schema digest
sha256:33a99e27e3c7178b506b333830e16c94682803eccf44c54051b6af0183e0ede3
source file sha256
sha256:31b1da211849d24a57c9af7636da46a5b82fc8a3ca1542bb3ebd8775e9a31cec
rows in public.atom
9111
rows in public.molecule
343

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-3d090a82-ceab-4c3d-bb4c-19e9c7a03d3b
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