Triple
T22401327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1982 World 600 |
E553767
|
entity |
| Predicate | averageSpeedMph |
P2060
|
FINISHED |
| Object | 129.326 |
—
|
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: 129.326 | Statement: [1982 World 600, averageSpeedMph, 129.326]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageSpeedMph Context triple: [1982 World 600, averageSpeedMph, 129.326]
-
A.
hasAverageSurfaceSpeed
chosen
Indicates the typical or mean speed at which something moves across a surface over a given period or distance.
-
B.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
C.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
D.
plannedSpeed
Indicates the intended or target speed that an entity is expected or scheduled to maintain, rather than its actual current speed.
-
E.
baseSpeed
Indicates the default or starting rate at which an entity moves or operates before any modifications or adjustments.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b4a96c8190838f5dda21c4d853 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.