Triple
T29750458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIM30 |
E752878
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York City express bus 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 express bus route Context triple: [SIM30, instanceOf, New York City express bus 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.
street in New York City
A street in New York City is a public urban thoroughfare lined with diverse buildings and infrastructure that supports vehicular, pedestrian, and commercial activity within the city's dense grid layout.
-
D.
New York City transit contract system
A New York City transit contract system is a coordinated framework of agreements, rules, and digital processes that govern how public transit services, fares, and infrastructure projects are procured, managed, and enforced across the city’s transportation network.
-
E.
local bus route
A local bus route is a designated path within a limited geographic area along which buses operate on a regular schedule to transport passengers between specific stops.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:53 p.m.