Triple

T21904432
Position Surface form Disambiguated ID Type / Status
Subject Final System Plan E540896 entity
Predicate describedRailroad P76977 FINISHED
Object Detroit, Toledo and Ironton Railroad 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: Detroit, Toledo and Ironton Railroad | Statement: [Final System Plan, describedRailroad, Detroit, Toledo and Ironton Railroad]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Detroit, Toledo and Ironton Railroad
Context triple: [Final System Plan, describedRailroad, Detroit, Toledo and Ironton Railroad]
  • A. Pere Marquette Railway
    Pere Marquette Railway was a historic Midwestern U.S. railroad company that operated primarily in Michigan and surrounding states in the late 19th and early 20th centuries.
  • B. Cleveland, Painesville and Ashtabula Railroad
    The Cleveland, Painesville and Ashtabula Railroad was a 19th-century rail line in northern Ohio that became a key predecessor to the Lake Shore and Michigan Southern Railway.
  • C. Lake Shore and Michigan Southern Railway
    The Lake Shore and Michigan Southern Railway was a major 19th-century American railroad that formed a key part of the New York Central system, linking the Great Lakes region with the Eastern United States.
  • D. Cleveland, Columbus and Cincinnati Railroad
    The Cleveland, Columbus and Cincinnati Railroad was a 19th-century American railway line in Ohio that connected major cities and played a key role in regional transportation and economic development.
  • E. Cleveland Railway
    Cleveland Railway was a major early 20th-century streetcar and public transit company serving the city of Cleveland, Ohio.
  • 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: Detroit, Toledo and Ironton Railroad
Target entity description: The Detroit, Toledo and Ironton Railroad was a regional U.S. railroad operating primarily in Michigan and Ohio, known for its freight services and later incorporation into larger rail systems.
  • A. Pere Marquette Railway
    Pere Marquette Railway was a historic Midwestern U.S. railroad company that operated primarily in Michigan and surrounding states in the late 19th and early 20th centuries.
  • B. Cleveland, Painesville and Ashtabula Railroad
    The Cleveland, Painesville and Ashtabula Railroad was a 19th-century rail line in northern Ohio that became a key predecessor to the Lake Shore and Michigan Southern Railway.
  • C. Lake Shore and Michigan Southern Railway
    The Lake Shore and Michigan Southern Railway was a major 19th-century American railroad that formed a key part of the New York Central system, linking the Great Lakes region with the Eastern United States.
  • D. Cleveland, Columbus and Cincinnati Railroad
    The Cleveland, Columbus and Cincinnati Railroad was a 19th-century American railway line in Ohio that connected major cities and played a key role in regional transportation and economic development.
  • E. Cleveland Railway
    Cleveland Railway was a major early 20th-century streetcar and public transit company serving the city of Cleveland, Ohio.
  • 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_69e0c47b4e8c81908c8076eaa4c8e4f2 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f121d4c0248190909172decd7cbc64 completed April 28, 2026, 9:08 p.m.
Created at: April 16, 2026, 7:29 p.m.