Triple
T17455742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reno Air Races |
E425022
|
entity |
| Predicate | raceSpeedRange |
P2096
|
FINISHED |
| Object | over 400 mph in top classes |
—
|
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: over 400 mph in top classes | Statement: [Reno Air Races, raceSpeedRange, over 400 mph in top classes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceSpeedRange Context triple: [Reno Air Races, raceSpeedRange, over 400 mph in top classes]
-
A.
maximumSpeedRecord
Indicates that an entity holds the highest recorded speed value (a speed record) within a given context or category.
-
B.
acceleration0To60mph
Indicates the rate or time it takes for something to increase its speed from 0 to 60 miles per hour.
-
C.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
D.
acceleration0To100Kmh
Indicates the rate or time it takes for something to accelerate from 0 to 100 kilometers per hour.
-
E.
0-200kmhTime
Indicates the time it takes for something, typically a vehicle, to accelerate from 0 to 200 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45141e1d48190b7de9159f1fd71fa |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.