Triple
T694601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Société de transport de Montréal |
E13868
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit authority |
C220
|
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 authority Context triple: [Société de transport de Montréal, instanceOf, public transit authority]
-
A.
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.
-
B.
public transportation agency
chosen
A public transportation agency is an organization responsible for planning, operating, and managing shared transit services such as buses, trains, and other modes to provide mobility for the public within a defined region.
-
C.
public transit safety oversight agency
A public transit safety oversight agency is a governmental or quasi-governmental body responsible for setting, monitoring, and enforcing safety standards and practices across public transportation systems to protect passengers, workers, and the public.
-
D.
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.
-
E.
mass transit operator
A mass transit operator is an entity responsible for managing, coordinating, and providing public transportation services such as buses, trains, or subways within a specific region or network.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:36 p.m.