Triple
T28372245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Subway rolling stock |
E718664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit vehicle type |
C53952
|
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: public transit vehicle type Context triple: [New York City Subway rolling stock, instanceOf, public transit vehicle type]
-
A.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
-
B.
public transit board
A public transit board is a governing body responsible for overseeing, setting policy for, and making strategic decisions about a region’s public transportation system.
-
C.
public transport technology
Public transport technology encompasses the systems, vehicles, infrastructure, and digital tools used to plan, operate, and optimize shared transportation services such as buses, trains, trams, and metros.
-
D.
public transportation infrastructure
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
-
E.
rubber-tired transit system
A rubber-tired transit system is a guided public transportation mode in which vehicles run on rubber tires along a dedicated roadway or track, often combining bus-like flexibility with rail-like guidance and capacity.
- F. None of above. chosen
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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1 a.m.