Triple
T8224242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMT lines |
E192138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of New York City Subway services |
C12143
|
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: group of New York City Subway services Context triple: [BMT lines, instanceOf, group of New York City Subway services]
-
A.
New York City Subway service designation
chosen
A New York City Subway service designation is a letter, number, or symbol that identifies a specific subway route, indicating its line, terminals, and general service pattern for riders.
-
B.
New York City Subway rolling stock class
A New York City Subway rolling stock class is a standardized group of subway cars sharing common design, technical specifications, and operational characteristics used on the NYC subway system.
-
C.
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.
-
D.
subway line
A subway line is a fixed route within an urban rail transit system, consisting of a sequence of stations and tracks over which trains operate according to a scheduled service.
-
E.
Long Island Rail Road service area
The Long Island Rail Road service area encompasses the network of commuter rail lines and stations extending from New York City through Nassau and Suffolk counties on Long Island, providing passenger rail service to communities across this 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:45 p.m.