Triple
T3765942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGV POS |
E82676
|
entity |
| Predicate | worldSpeedRecord |
P12248
|
FINISHED |
| Object | 574.8 km/h |
—
|
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: 574.8 km/h | Statement: [TGV POS, worldSpeedRecord, 574.8 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldSpeedRecord Context triple: [TGV POS, worldSpeedRecord, 574.8 km/h]
-
A.
worldRecordSetOn
Indicates that a world record was achieved or established on a specific date or occasion.
-
B.
wasWorldRecordFor
Indicates that something held the status of being the best performance or highest achievement ever recorded for a particular event, category, or metric at a given time.
-
C.
worldRegionTallestRecord
Indicates that an entity holds the record for being the tallest within a specified world region.
-
D.
isAllTimeRecordHolderFor
Indicates that an entity holds the highest or best performance record of all time for a particular category, event, or metric.
-
E.
speedAchieved
chosen
Indicates that a particular speed has been reached or attained by an entity during an event or action.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbfeb52081909c38103beb5dbdcd |
completed | March 8, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.