Triple
T38032030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M86 Select Bus Service |
E948936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York City Select Bus Service route |
C18347
|
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: New York City Select Bus Service route Context triple: [M86 Select Bus Service, instanceOf, New York City Select Bus Service route]
-
A.
New York City bus route
chosen
A New York City bus route is a designated public transit service path, identified by a route number or letter, that specifies the sequence of streets and stops a city bus follows on a scheduled basis.
-
B.
New York City transit line
A New York City transit line is a designated route within the city's public transportation network, typically identified by a letter, number, or color, that connects multiple stations or stops across specific boroughs and neighborhoods.
-
C.
DC Circulator line
A DC Circulator line is a specific bus route within Washington, D.C.’s Circulator transit system that provides frequent, low-cost service along a defined corridor connecting key neighborhoods and destinations.
-
D.
bus rapid transit line
A bus rapid transit line is a high-capacity bus corridor that uses dedicated lanes, priority signaling, and streamlined stations to provide fast, reliable, rail-like transit service.
-
E.
Long Island Rail Road line
A Long Island Rail Road line is a specific passenger rail route within the LIRR network that connects designated terminals and intermediate stations across Long Island and the greater New York City area.
- 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.