Triple
T36437479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelby GT500 (2020–2022) |
E897626
|
entity |
| Predicate | 0to60mph |
P8445
|
FINISHED |
| Object | about 3.3 seconds |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: about 3.3 seconds | Statement: [Shelby GT500 (2020–2022), 0to60mph, about 3.3 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 0to60mph Context triple: [Shelby GT500 (2020–2022), 0to60mph, about 3.3 seconds]
-
A.
acceleration0To60mph
chosen
Indicates the rate or time it takes for something to increase its speed from 0 to 60 miles per hour.
-
B.
acceleration0To100Kmh
Indicates the rate or time it takes for something to accelerate from 0 to 100 kilometers per hour.
-
C.
governingSpeedRange
Indicates the range of speeds within which a governing or limiting mechanism is intended to operate or apply.
-
D.
accelerationTimeToTopSpeed
Indicates the duration required for something to increase its speed from an initial value to its maximum (top) speed.
-
E.
acceleration0To300kmh
Indicates the rate or time it takes for something to increase its speed from 0 to 300 kilometers per hour.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.