Triple
T16639055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrono app |
E404282
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit mobile application |
C14195
|
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 mobile application Context triple: [Chrono app, instanceOf, public transit mobile application]
-
A.
public transit app
chosen
A public transit app is a mobile or web application that helps users plan, navigate, and track journeys using buses, trains, subways, and other shared transportation services in real time.
-
B.
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.
-
C.
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.
-
D.
mobile banking application
A mobile banking application is a secure software platform that enables users to manage their financial accounts, perform transactions, and access banking services directly from their mobile devices.
-
E.
mobile application feature
A mobile application feature is a distinct, user-facing capability or function within a mobile app that enables users to perform specific tasks or achieve particular goals.
- 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.