Triple
T5350944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukon Striker |
E124175
|
entity |
| Predicate | hasTrainConfiguration |
P26476
|
FINISHED |
| Object | three rows per car |
—
|
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: three rows per car | Statement: [Yukon Striker, hasTrainConfiguration, three rows per car]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainConfiguration Context triple: [Yukon Striker, hasTrainConfiguration, three rows per car]
-
A.
hasRailConfiguration
Indicates that an entity is associated with, or characterized by, a particular arrangement or setup of rails.
-
B.
trainConfiguration
chosen
Indicates the specific arrangement and composition of train elements (such as locomotives and cars) used together for a particular operation or service.
-
C.
trainTypeUsed
Indicates that a specific type or category of train is employed or operated in a given context or service.
-
D.
usesTrainNumber
Indicates that one entity operates, identifies, or references another entity by a specific train number.
-
E.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd861188ac81908ef2b1f25cc6c864 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.