Triple
T22112874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun Shuttle |
E546460
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | demand-responsive transport service |
C35830
|
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 service Context triple: [Sun Shuttle, instanceOf, demand-responsive transport service]
-
A.
demand-responsive bus service
chosen
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.
-
B.
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.
-
C.
multimodal transport platform
A multimodal transport platform is an integrated system that coordinates and optimizes the planning, booking, and management of journeys across multiple transportation modes (such as rail, road, air, and sea) through a unified digital interface.
-
D.
public transport service feature
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.
-
E.
paratransit operator
A paratransit operator is a transportation service provider that offers flexible, demand-responsive rides—often door-to-door—for individuals whose disabilities or mobility limitations prevent them from using standard public transit.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:31 p.m.