Triple
T38344631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRT Division (limited connections and yards only) |
E1041505
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of New York City Subway |
C14640
|
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: component of New York City Subway Context triple: [IRT Division (limited connections and yards only), instanceOf, component of New York City Subway]
-
A.
New York City Subway rolling stock class
A New York City Subway rolling stock class is a standardized group of subway cars sharing common design, technical specifications, and operational characteristics used on the NYC subway system.
-
B.
New York City Subway terminal
A New York City Subway terminal is a subway station where one or more train lines begin or end their scheduled service, typically featuring multiple tracks, crew facilities, and track arrangements for turning trains around.
-
C.
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.
-
D.
New York City Subway station platform
A New York City Subway station platform is the designated area within an underground, elevated, or at-grade station where passengers wait for, board, and alight subway trains, typically equipped with safety features, signage, and access points like stairs, elevators, and turnstiles.
-
E.
New York City Subway yard
chosen
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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.