Triple
T3782717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STM mobile app |
E85456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit app |
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 app Context triple: [STM mobile app, instanceOf, public transit app]
-
A.
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.
-
B.
public transit brand
A public transit brand is the cohesive identity—encompassing name, visuals, messaging, and perceived values—that distinguishes a transit agency’s services and shapes how riders recognize, trust, and experience the system.
-
C.
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.
-
D.
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.
-
E.
public transit customer service facility network
A public transit customer service facility network is a coordinated system of physical and/or virtual locations where transit users can obtain information, purchase or manage fare products, resolve service issues, and access support related to public transportation services.
- F. None of above. chosen
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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:13 p.m.