Triple
T24571724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bethesda Circulator bus services |
E607979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bus transit service |
C35829
|
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: bus transit service Context triple: [Bethesda Circulator bus services, instanceOf, bus transit service]
-
A.
bus service network
A bus service network is an interconnected system of bus routes, stops, schedules, and vehicles designed to transport passengers efficiently across a defined geographic area.
-
B.
regional bus service
A regional bus service is a public transportation system that operates scheduled bus routes connecting multiple towns or cities within a specific geographic area.
-
C.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
-
D.
feeder bus service
A feeder bus service is a local transit route that connects neighborhoods or outlying areas to major transportation hubs or mainline routes, facilitating convenient transfers and extended network access.
-
E.
fixed-route transit service
chosen
Fixed-route transit service is a public transportation mode that operates vehicles along predetermined paths with scheduled stops and timetables, regardless of individual passenger requests.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:28 a.m.