Triple
T10375417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bus Tracker real-time information system |
E244494
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | real-time passenger information system |
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: real-time passenger information system Context triple: [Bus Tracker real-time information system, instanceOf, real-time passenger information system]
-
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 transport ticketing system
A public transport ticketing system manages the purchase, validation, and tracking of fares and passes for passengers across various transit services.
-
C.
passenger rail terminal
A passenger rail terminal is a dedicated facility where travelers board, disembark, and transfer between trains, supported by platforms, ticketing, waiting areas, and related passenger services.
-
D.
public transit fare payment system
A public transit fare payment system manages the calculation, collection, validation, and tracking of passenger payments across various transit services and media (e.g., cards, mobile apps, tickets) to authorize and record travel.
-
E.
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.
- 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.