Triple
T20088791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York, Chicago and St. Louis Railroad |
E496209
|
entity |
| Predicate | mainLineRoute |
P24771
|
FINISHED |
| Object | Cleveland–St. Louis |
—
|
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: Cleveland–St. Louis | Statement: [New York, Chicago and St. Louis Railroad, mainLineRoute, Cleveland–St. Louis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cleveland–St. Louis Context triple: [New York, Chicago and St. Louis Railroad, mainLineRoute, Cleveland–St. Louis]
-
A.
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.
-
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.
Chicago–St. Louis corridor
The Chicago–St. Louis corridor is a major Midwestern passenger rail route linking Chicago, Illinois, with St. Louis, Missouri, and serving as a key segment of Amtrak’s intercity service.
-
D.
Pittsburgh–Cincinnati
Pittsburgh–Cincinnati refers to the intercity rail corridor linking Pittsburgh, Pennsylvania, and Cincinnati, Ohio, historically used by passenger and freight trains.
-
E.
St. Louis metropolitan area
The St. Louis metropolitan area is a bi-state urban region centered on the city of St. Louis, spanning parts of Missouri and Illinois and serving as a major Midwestern hub for culture, education, and industry.
- 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: Cleveland–St. Louis Target entity description: Cleveland–St. Louis was a principal intercity rail corridor in the Midwestern United States that connected Cleveland, Ohio, with St. Louis, Missouri.
-
A.
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.
-
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.
Chicago–St. Louis corridor
The Chicago–St. Louis corridor is a major Midwestern passenger rail route linking Chicago, Illinois, with St. Louis, Missouri, and serving as a key segment of Amtrak’s intercity service.
-
D.
Pittsburgh–Cincinnati
Pittsburgh–Cincinnati refers to the intercity rail corridor linking Pittsburgh, Pennsylvania, and Cincinnati, Ohio, historically used by passenger and freight trains.
-
E.
St. Louis metropolitan area
The St. Louis metropolitan area is a bi-state urban region centered on the city of St. Louis, spanning parts of Missouri and Illinois and serving as a major Midwestern hub for culture, education, and industry.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655d65a88190a510132f36341b6c |
completed | April 20, 2026, 5:41 p.m. |
Created at: April 11, 2026, 11:18 p.m.