Triple
T12922199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTA New York City Transit Subdivision B |
E309151
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rapid transit operating division |
C1888
|
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: rapid transit operating division Context triple: [MTA New York City Transit Subdivision B, instanceOf, rapid transit operating division]
-
A.
rapid transit division
chosen
A rapid transit division is an organizational unit within a transportation agency responsible for planning, operating, and maintaining high-frequency, high-capacity urban rail or bus rapid transit services.
-
B.
rapid transit line group
A rapid transit line group is a collection of closely related or jointly operated rapid transit lines that share infrastructure, service patterns, or branding within a transit network.
-
C.
rapid transit line
A rapid transit line is a high-capacity, high-frequency urban rail route operating on an exclusive or mostly separated right-of-way to provide fast, reliable public transportation between key areas of a city or metropolitan region.
-
D.
railroad operating division
A railroad operating division is a geographically defined segment of a railway system managed as a unit for train operations, crew assignments, dispatching, and maintenance activities.
-
E.
historical transit operating division
A historical transit operating division is an organizational unit within a past or legacy public transportation system responsible for managing and coordinating transit services, personnel, and resources within a specific geographic area or operational domain.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:42 p.m.