Triple
T36984669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri state transportation system |
E914928
|
entity |
| Predicate | includesAmtrakRoute |
P167447
|
FINISHED |
| Object | Missouri River Runner |
E119237
|
NE 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: Missouri River Runner | Statement: [Missouri state transportation system, includesAmtrakRoute, Missouri River Runner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAmtrakRoute Context triple: [Missouri state transportation system, includesAmtrakRoute, Missouri River Runner]
-
A.
hasAmtrakStationStatus
Indicates whether and how an entity is served by an Amtrak station, such as its operational or service status.
-
B.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
C.
amtrakLine
chosen
Indicates that one entity is an Amtrak-operated rail line serving or connecting the other entity.
-
D.
isPassengerRail
Indicates that something functions as or is classified as a passenger rail service or system, primarily used to transport people rather than freight.
-
E.
amtrakServiceType
Indicates the specific category or type of Amtrak rail service that applies to a given route, trip, or train.
- F. None of above.
Provenance (4 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c50ed608190a8b35108c0449f75 |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.