Triple

T2382545
Position Surface form Disambiguated ID Type / Status
Subject PortsToronto E46342 entity
Predicate instanceOf P0 FINISHED
Object transportation infrastructure operator C6404 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: transportation infrastructure operator
Context triple: [PortsToronto, instanceOf, transportation infrastructure operator]
  • A. transport infrastructure operator chosen
    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.
  • B. 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.
  • C. toll road operator
    A toll road operator is an entity responsible for managing, maintaining, and collecting user fees on designated roadways or bridges, often under government concession or private ownership.
  • D. 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.
  • E. 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.
  • 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_69a88a1554a48190a0180682bcf099be completed March 4, 2026, 7:37 p.m.
Created at: March 4, 2026, 7:57 p.m.