Triple
T11798452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BC Rapid Transit Company |
E280562
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit operating company |
C221
|
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 operating company Context triple: [BC Rapid Transit Company, instanceOf, public transit operating company]
-
A.
mass transit operator
chosen
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.
-
B.
paratransit operator
A paratransit operator is a transportation service provider that offers flexible, demand-responsive rides—often door-to-door—for individuals whose disabilities or mobility limitations prevent them from using standard public transit.
-
C.
transport infrastructure operator
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
-
D.
transportation network company
A transportation network company is a business that uses digital platforms, typically mobile apps, to connect passengers with drivers who provide on-demand transportation services.
-
E.
transportation services company
A transportation services company is an organization that plans, manages, and operates the movement of people or goods using various modes of transport, such as road, rail, air, or sea, often providing logistics, scheduling, and support services.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.