gold
SELECT T.element FROM atom AS T WHERE T.molecule_id = 'TR000' ORDER BY T.element LIMIT 3
- T.element
- ascending
sha256:e0358e4b2184517a7f71f6597dac3e4c69c5b9094b2e7d5f461a8bd46b864ca2
R-ORD GOLD-ONLY duplicate-full-row
toxicology · dev_20251106-00000-of-00001 from https://huggingface.co/datasets/birdsql/bird_sql_dev_20251106/resolve/3c11fb193e5439b338e23677fa0aae11e8b85db9/data/dev_20251106-00000-of-00001.json (commit 3c11fb19, downloaded 2026-09-07)
Please list the top three elements in the molecule TR000 in alphabetical order.
the hint the set supplies: TR000 is the molecule id.
This question was audited without a prediction beside it, so there is nothing to compare the gold with. The probes below read the gold alone.
SELECT T.element FROM atom AS T WHERE T.molecule_id = 'TR000' ORDER BY T.element LIMIT 3
sha256:e0358e4b2184517a7f71f6597dac3e4c69c5b9094b2e7d5f461a8bd46b864ca2
from evidence-gold.json, 3 rows
| elementTEXT |
|---|
| c |
| cl |
| cl |
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
{
"heuristic": true,
"keys": [
{
"key": "T.element",
"column": "atom.element",
"declared_type": "TEXT",
"not_applicable": null,
"census": {
"rows": 12333,
"nulls": 0,
"empty_strings": 0,
"non_numeric": 12333,
"pattern": "^-?[0-9]+(\\.[0-9]+)?$"
},
"every_value_is_numeric": false
}
]
}
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
{
"heuristic": true,
"cut": 3,
"offset": 0,
"distinct_kept": false,
"unbounded_sql": "SELECT T.element, T.element AS attestql_ordering_key_0 FROM atom AS T WHERE T.molecule_id = 'TR000' ORDER BY T.element",
"unbounded_rows": 5,
"projected_columns": [
"element"
],
"ordering_key_columns": [
"attestql_ordering_key_0"
],
"ordering_keys": [
{
"key": "T.element",
"direction": "asc",
"nulls": "first",
"nulls_first_in_effect": true,
"returned_rows_null_in_this_key": 0,
"fires": false
}
],
"tied_at_the_cut": {
"positions": [
1,
2,
3
],
"tied_rows": 3,
"distinct_projected_answers": 1,
"rows": [
[
{
"type": "str",
"value": "cl"
}
],
[
{
"type": "str",
"value": "cl"
}
],
[
{
"type": "str",
"value": "cl"
}
]
]
},
"case": null
}
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-ORD",
"baseline_result_hash": "sha256:e0358e4b2184517a7f71f6597dac3e4c69c5b9094b2e7d5f461a8bd46b864ca2",
"baseline_result": {
"columns": [
{
"name": "element",
"declared_type": "TEXT"
}
],
"row_count": 3,
"truncated": false,
"rows_shown": 3,
"rows": [
[
{
"type": "str",
"value": "c"
}
],
[
{
"type": "str",
"value": "cl"
}
],
[
{
"type": "str",
"value": "cl"
}
]
],
"result_hash": "sha256:e0358e4b2184517a7f71f6597dac3e4c69c5b9094b2e7d5f461a8bd46b864ca2"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"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:e0358e4b2184517a7f71f6597dac3e4c69c5b9094b2e7d5f461a8bd46b864ca2",
"result": {
"columns": [
{
"name": "element",
"declared_type": "TEXT"
}
],
"row_count": 3,
"truncated": false,
"rows_shown": 3,
"rows": [
[
{
"type": "str",
"value": "c"
}
],
[
{
"type": "str",
"value": "cl"
}
],
[
{
"type": "str",
"value": "cl"
}
]
],
"result_hash": "sha256:e0358e4b2184517a7f71f6597dac3e4c69c5b9094b2e7d5f461a8bd46b864ca2"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}
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
from smells.json, 1 row
| cl |
{
"heuristic": true,
"rows": 3,
"distinct_rows": 2,
"repeated_rows": 1,
"largest_repeat": 2,
"result_bounded": false,
"distinct_stated": false,
"set_operation": false,
"repeats_of_the_rows_shown": [
2
]
}
SELECT T.element FROM atom AS T WHERE T.molecule_id = 'TR000' ORDER BY T.element LIMIT 3
result_hash sha256:e0358e4b2184517a7f71f6597dac3e4c69c5b9094b2e7d5f461a8bd46b864ca2 recomputed from this JSON: match
record_hash sha256:02a7c48432128782756bf7acbdb8c809332f085b4dba722a82dda3681b0e722b recomputed from this JSON: match
from evidence-gold.json, 3 rows
| elementTEXT |
|---|
| c |
| cl |
| cl |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/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-ORD