Triple
T51145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Department of Transportation |
E1003
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation authority |
C221
|
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: transportation authority Context triple: [New York City Department of Transportation, instanceOf, transportation authority]
-
A.
public transportation agency
A public transportation agency is an organization responsible for planning, operating, and managing shared transit services such as buses, trains, and other modes to provide mobility for the public within a defined region.
-
B.
mass transit operator
chosen
A mass transit operator is an entity responsible for managing, coordinating, and providing public transportation services such as buses, trains, or subways within a specific region or network.
-
C.
transport hub
A transport hub is a central location where multiple modes or routes of transportation intersect, enabling the efficient transfer of passengers or goods between them.
-
D.
commuter rail station
A commuter rail station is a designated facility where passengers board and alight regional trains that connect suburbs or outlying areas with urban centers, typically offering platforms, ticketing, and basic passenger amenities.
-
E.
rapid transit station
A rapid transit station is a designated facility where passengers board, alight, and transfer between high-frequency urban rail or metro services, typically featuring platforms, ticketing areas, and access to surrounding streets or other transport modes.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.