Triple
T8224243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMT lines |
E192138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former private transit division |
C1889
|
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: former private transit division Context triple: [BMT lines, instanceOf, former private transit division]
-
A.
historical transit operating division
chosen
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.
-
B.
former transit line
A former transit line is a previously operational public transportation route, such as a bus, tram, or rail line, that has been permanently discontinued or replaced.
-
C.
rapid transit division
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.
-
D.
public transit operations division
The public transit operations division is responsible for planning, scheduling, managing, and overseeing the daily operation and performance of a region’s public transportation services.
-
E.
former British Rail sector
A former British Rail sector is an organizational division that once managed specific types of rail services or geographic areas within the state-owned British Rail system before its restructuring and privatization.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:45 p.m.