Triple

T26278575
Position Surface form Disambiguated ID Type / Status
Subject IND Queens–Manhattan river crossings E660640 entity
Predicate instanceOf P0 FINISHED
Object New York City Subway tunnel complex C16245 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 tunnel complex
Context triple: [IND Queens–Manhattan river crossings, instanceOf, New York City Subway tunnel complex]
  • A. New York City Subway tunnel chosen
    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.
  • B. New York City water tunnel
    A New York City water tunnel is a large underground aqueduct system that transports potable water from upstate reservoirs to the city’s distribution network.
  • 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–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.
  • E. New York City Subway yard
    A New York City Subway yard is a specialized facility where subway trains are stored, inspected, maintained, and dispatched between periods of service.
  • 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_69ee812960d081909cff6085cc9fa3a6 completed April 26, 2026, 9:18 p.m.
Created at: April 26, 2026, 9:58 p.m.