Triple
T10375418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bus Tracker real-time information system |
E244494
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit information service |
C11180
|
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: public transit information service Context triple: [Bus Tracker real-time information system, instanceOf, public transit information service]
-
A.
public transport information system
chosen
A public transport information system is a software platform that collects, processes, and disseminates real-time and scheduled data about public transit services to passengers, operators, and other stakeholders.
-
B.
public transit station
A public transit station is a designated facility where passengers can access, board, transfer between, and disembark from public transportation services such as buses, trains, or subways.
-
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.
public transit plan
A public transit plan is a structured strategy that outlines routes, schedules, resources, and policies to provide efficient, accessible, and sustainable transportation services within a community or region.
-
E.
public transit route
A public transit route is a predefined path with designated stops and schedules along which public transportation vehicles (such as buses, trams, or trains) operate to move passengers between locations.
- 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.