Triple
T10375514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pace On Demand services |
E244496
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | demand-responsive transport |
C911
|
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: demand-responsive transport Context triple: [Pace On Demand services, instanceOf, demand-responsive transport]
-
A.
rubber-tired transit system
A rubber-tired transit system is a guided public transportation mode in which vehicles run on rubber tires along a dedicated roadway or track, often combining bus-like flexibility with rail-like guidance and capacity.
-
B.
continuous transport system
A continuous transport system is a material handling arrangement that moves goods or resources in an uninterrupted flow along a fixed path using devices such as conveyors, pipelines, or automated tracks.
-
C.
public transit system
chosen
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.
rapid transit vehicle
A rapid transit vehicle is a high-capacity, electrically powered rail car or train designed to provide frequent, fast, and reliable urban or suburban passenger transportation on dedicated or grade-separated tracks.
-
E.
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.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:02 p.m.