gold
SELECT hero_id FROM hero_attribute WHERE attribute_value = ( SELECT MIN(attribute_value) FROM hero_attribute )
this statement states no ordering of its own
sha256:6102a64a3de4715970a6fda67a49780c4f33d8a2fe0c08f5be88d4c84de85b4a
R-SET GOLD-ONLY duplicate-full-row
superhero · 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)
Give the hero ID of superhero with the lowest attribute value.
the hint the set supplies: lowest attribute value refers to MIN(attribute_value);
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 hero_id FROM hero_attribute WHERE attribute_value = ( SELECT MIN(attribute_value) FROM hero_attribute )
this statement states no ordering of its own
sha256:6102a64a3de4715970a6fda67a49780c4f33d8a2fe0c08f5be88d4c84de85b4a
from evidence-gold.json, 10 rows
| hero_idINTEGER |
|---|
| 283 |
| 397 |
| 416 |
| 508 |
| 558 |
| 586 |
| 276 |
| 276 |
| 276 |
| 276 |
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:6102a64a3de4715970a6fda67a49780c4f33d8a2fe0c08f5be88d4c84de85b4a",
"baseline_result": {
"columns": [
{
"name": "hero_id",
"declared_type": "INTEGER"
}
],
"row_count": 10,
"truncated": false,
"rows_shown": 10,
"rows": [
[
{
"type": "int",
"value": 283
}
],
[
{
"type": "int",
"value": 397
}
],
[
{
"type": "int",
"value": 416
}
],
[
{
"type": "int",
"value": 508
}
],
[
{
"type": "int",
"value": 558
}
],
[
{
"type": "int",
"value": 586
}
],
[
{
"type": "int",
"value": 276
}
],
[
{
"type": "int",
"value": 276
}
],
[
{
"type": "int",
"value": 276
}
],
[
{
"type": "int",
"value": 276
}
]
],
"result_hash": "sha256:6102a64a3de4715970a6fda67a49780c4f33d8a2fe0c08f5be88d4c84de85b4a"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"hero_attribute"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:528e1135d8125a4d0e8d572e99773f904171c36883804eab7e392e704f38a1f7",
"result": {
"columns": [
{
"name": "hero_id",
"declared_type": "INTEGER"
}
],
"row_count": 10,
"truncated": false,
"rows_shown": 10,
"rows": [
[
{
"type": "int",
"value": 276
}
],
[
{
"type": "int",
"value": 558
}
],
[
{
"type": "int",
"value": 276
}
],
[
{
"type": "int",
"value": 586
}
],
[
{
"type": "int",
"value": 508
}
],
[
{
"type": "int",
"value": 416
}
],
[
{
"type": "int",
"value": 276
}
],
[
{
"type": "int",
"value": 283
}
],
[
{
"type": "int",
"value": 276
}
],
[
{
"type": "int",
"value": 397
}
]
],
"result_hash": "sha256:528e1135d8125a4d0e8d572e99773f904171c36883804eab7e392e704f38a1f7"
}
},
"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
| 276 |
{
"heuristic": true,
"rows": 10,
"distinct_rows": 7,
"repeated_rows": 1,
"largest_repeat": 4,
"result_bounded": false,
"distinct_stated": false,
"set_operation": false,
"repeats_of_the_rows_shown": [
4
]
}
SELECT hero_id FROM hero_attribute WHERE attribute_value = ( SELECT MIN(attribute_value) FROM hero_attribute )
result_hash sha256:6102a64a3de4715970a6fda67a49780c4f33d8a2fe0c08f5be88d4c84de85b4a recomputed from this JSON: match
record_hash sha256:2d2510c80d0f8d618e594f38a8779ad51dee0a73b3eae9dd7d52d553a001df57 recomputed from this JSON: match
from evidence-gold.json, 10 rows
| hero_idINTEGER |
|---|
| 283 |
| 397 |
| 416 |
| 508 |
| 558 |
| 586 |
| 276 |
| 276 |
| 276 |
| 276 |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/superhero/superhero.sqlite | size=237568 under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET