Triple
T2921799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMT |
E78743
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Brooklyn–Manhattan Transit Corporation |
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: Brooklyn–Manhattan Transit Corporation Context triple: [BMT, instanceOf, Brooklyn–Manhattan Transit Corporation]
-
A.
division of Metropolitan Transportation Authority
A division of the Metropolitan Transportation Authority is an organizational unit responsible for managing and operating a specific set of transit services, assets, or functions within the broader MTA system.
-
B.
street railway company
A street railway company is a business entity that owns, operates, and maintains streetcars or trams running on fixed rails along public streets to provide urban passenger transportation.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:54 p.m.