Triple
T20179075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago, Burlington and Quincy Railroad |
E492677
|
entity |
| Predicate | operatedRoute |
P18593
|
FINISHED |
| Object | Chicago–Omaha |
—
|
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–Omaha | Statement: [Chicago, Burlington and Quincy Railroad, operatedRoute, Chicago–Omaha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chicago–Omaha Context triple: [Chicago, Burlington and Quincy Railroad, operatedRoute, Chicago–Omaha]
-
A.
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.
-
B.
Buffalo–Cleveland–Chicago
Buffalo–Cleveland–Chicago refers to a major intercity rail corridor in the Great Lakes region that connected these three cities as part of a key route of the New York, Chicago and St. Louis Railroad.
-
C.
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.
-
D.
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.
-
E.
Chicago and Milwaukee
Chicago and Milwaukee are two major Midwestern U.S. cities located along the southwestern shore of Lake Michigan, known for their cultural, economic, and historical significance.
- 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–Omaha Target entity description: 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.
-
A.
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.
-
B.
Buffalo–Cleveland–Chicago
Buffalo–Cleveland–Chicago refers to a major intercity rail corridor in the Great Lakes region that connected these three cities as part of a key route of the New York, Chicago and St. Louis Railroad.
-
C.
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.
-
D.
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.
-
E.
Chicago and Milwaukee
Chicago and Milwaukee are two major Midwestern U.S. cities located along the southwestern shore of Lake Michigan, known for their cultural, economic, and historical significance.
- 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.