Triple
T20179076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago, Burlington and Quincy Railroad |
E492677
|
entity |
| Predicate | operatedRoute |
P18593
|
FINISHED |
| Object | Chicago–Kansas City |
—
|
NE NERFINISHED |
How this triple was built (3 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: Chicago–Kansas City | Statement: [Chicago, Burlington and Quincy Railroad, operatedRoute, Chicago–Kansas City]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chicago–Kansas City Context triple: [Chicago, Burlington and Quincy Railroad, operatedRoute, Chicago–Kansas City]
-
A.
Chicago–Omaha
Chicago–Omaha was a key Midwestern rail corridor linking Chicago, Illinois, with Omaha, Nebraska, and serving as an important route for both passenger and freight traffic.
-
B.
Cleveland–St. Louis
Cleveland–St. Louis was a principal intercity rail corridor in the Midwestern United States that connected Cleveland, Ohio, with St. Louis, Missouri.
-
C.
Chicago–Denver
Chicago–Denver was a major long-distance passenger and freight rail route linking Chicago, Illinois, with Denver, Colorado, across the American Midwest and Great Plains.
-
D.
St. Louis–Dallas
St. Louis–Dallas refers to the intercity rail corridor linking St. Louis, Missouri, with Dallas, Texas, historically served by passenger trains such as the Texas Special.
-
E.
Pittsburgh–St. Louis
Pittsburgh–St. Louis refers to the intercity rail corridor linking Pittsburgh, Pennsylvania, with St. Louis, Missouri, historically used by major Midwestern and Eastern railroads.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Chicago–Kansas City Target entity description: Chicago–Kansas City is a major Midwestern rail corridor linking Chicago, Illinois, with Kansas City, Missouri, serving as an important freight and passenger route.
-
A.
Chicago–Omaha
Chicago–Omaha was a key Midwestern rail corridor linking Chicago, Illinois, with Omaha, Nebraska, and serving as an important route for both passenger and freight traffic.
-
B.
Cleveland–St. Louis
Cleveland–St. Louis was a principal intercity rail corridor in the Midwestern United States that connected Cleveland, Ohio, with St. Louis, Missouri.
-
C.
Chicago–Denver
Chicago–Denver was a major long-distance passenger and freight rail route linking Chicago, Illinois, with Denver, Colorado, across the American Midwest and Great Plains.
-
D.
St. Louis–Dallas
St. Louis–Dallas refers to the intercity rail corridor linking St. Louis, Missouri, with Dallas, Texas, historically served by passenger trains such as the Texas Special.
-
E.
Pittsburgh–St. Louis
Pittsburgh–St. Louis refers to the intercity rail corridor linking Pittsburgh, Pennsylvania, with St. Louis, Missouri, historically used by major Midwestern and Eastern railroads.
- F. None of above. chosen
Provenance (2 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668ed07c8819091bd9ffda237a91c |
completed | April 20, 2026, 5:57 p.m. |
Created at: April 11, 2026, 11:36 p.m.