Triple
T28012675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MobilityPLUS paratransit service |
E707459
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | accessible public transportation service |
C15962
|
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: accessible public transportation service Context triple: [MobilityPLUS paratransit service, instanceOf, accessible public transportation service]
-
A.
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.
-
B.
public transport service feature
chosen
A public transport service feature is a specific characteristic, function, or amenity of a public transportation offering that affects how passengers access, experience, and evaluate the service.
-
C.
public transportation infrastructure
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
-
D.
demand-responsive bus service
A demand-responsive bus service is a flexible public transport system where routes and schedules are dynamically adjusted based on real-time passenger requests rather than fixed timetables and stops.
-
E.
transportation service
A transportation service is a system or business that moves people or goods from one location to another using various modes of transport under defined schedules, routes, and conditions.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 8:04 p.m.