Triple
T3890355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGV Atlantique trainset |
E88045
|
entity |
| Predicate | worldSpeedRecordHolder |
P29425
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [TGV Atlantique trainset, worldSpeedRecordHolder, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldSpeedRecordHolder Context triple: [TGV Atlantique trainset, worldSpeedRecordHolder, yes]
-
A.
worldSpeedRecordContext
Indicates the contextual circumstances (such as event, conditions, or category) under which a world speed record is set or recognized.
-
B.
isAllTimeRecordHolderFor
chosen
Indicates that an entity holds the highest or best performance record of all time for a particular category, event, or metric.
-
C.
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.
-
D.
worldRecordSetOn
Indicates that a world record was achieved or established on a specific date or occasion.
-
E.
worldRegionTallestRecord
Indicates that an entity holds the record for being the tallest within a specified world region.
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecb0ba448190aa076865b7762002 |
completed | March 9, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.