Triple
T16639057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrono app |
E404282
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | real-time transit tracking app |
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 transit tracking app Context triple: [Chrono app, instanceOf, real-time transit tracking app]
-
A.
traffic and navigation app
A traffic and navigation app is a mobile or web-based application that provides real-time route guidance, traffic conditions, and travel time estimates to help users efficiently reach their destinations.
-
B.
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.
-
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 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.
-
E.
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.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:18 a.m.