Triple
T7226352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri–Kansas–Texas Railroad |
E154788
|
entity |
| Predicate | railClass |
P5618
|
FINISHED |
| Object | Class I railroad |
—
|
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: Class I railroad | Statement: [Missouri–Kansas–Texas Railroad, railClass, Class I railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railClass Context triple: [Missouri–Kansas–Texas Railroad, railClass, Class I railroad]
-
A.
railroadClass
chosen
Indicates the classification or category of a railroad according to an established system (e.g., by size, revenue, or regulatory status).
-
B.
trainTypeUsed
Indicates that a specific type or category of train is employed or operated in a given context or service.
-
C.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
D.
operatedRollingStockClass
Indicates that an entity (such as a company or operator) has operated a specific class or type of rolling stock (e.g., trains or rail vehicles).
-
E.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9de21e081908f30700f6211c5ef |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.