Triple
T20179415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer Zephyr |
E492685
|
entity |
| Predicate | recordRunAverageSpeed |
P99339
|
FINISHED |
| Object | about 77 mph |
—
|
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 77 mph | Statement: [Pioneer Zephyr, recordRunAverageSpeed, about 77 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordRunAverageSpeed Context triple: [Pioneer Zephyr, recordRunAverageSpeed, about 77 mph]
-
A.
hourRecordDistance
Indicates that one entity holds or represents the record for the greatest distance covered within a one-hour time period relative to another entity or context.
-
B.
longDistanceRecordAverageSpeed
chosen
Indicates the average speed achieved over the course of a long-distance record attempt or performance.
-
C.
raceRecord
Indicates that there exists a recorded result or performance entry for an entity participating in a race or competitive event.
-
D.
previousRecordSpeed
Indicates that one record speed precedes another in time, representing the earlier benchmark before a new speed is achieved.
-
E.
trackRecordDistance
Indicates that one entity holds the record for the greatest distance achieved in a particular tracking or performance context.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668edf27881909820f9103e72533e |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.