Triple

T19056292
Position Surface form Disambiguated ID Type / Status
Subject Bronx elevated lines E466404 entity
Predicate instanceOf P0 FINISHED
Object New York City Subway predecessor C40576 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07 
Target class: New York City Subway predecessor
Context triple: [Bronx elevated lines, instanceOf, New York City Subway predecessor]
  • A. predecessor of New York City Subway line chosen
    A predecessor of a New York City Subway line is a historical transit service, route, or company whose operations, infrastructure, or numbering evolved into or were incorporated into the present-day subway line.
  • B. former New York City Subway station
    A former New York City Subway station is a decommissioned or abandoned stop that once served passengers on the NYC Subway system but is no longer in regular operation.
  • C. New York City Subway infrastructure project
    A New York City Subway infrastructure project is a coordinated planning, construction, and modernization effort aimed at building, upgrading, or maintaining the physical and technological systems that support subway service across the city.
  • D. New York City Subway tunnel
    A New York City Subway tunnel is an underground passageway engineered to safely guide subway trains, utilities, and related infrastructure beneath the city’s surface between stations.
  • E. New York City Subway–railroad interchange
    A New York City Subway–railroad interchange is a facility or location where subway lines physically connect with or provide direct transfer to mainline or commuter rail services, enabling passenger and sometimes equipment movement between the two systems.
  • F. None of above.

Provenance (1 batch)

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_69d8dd040fb881909af2a964f65ad208 completed April 10, 2026, 11:20 a.m.
Created at: April 10, 2026, 12:03 p.m.