Triple

T15422629
Position Surface form Disambiguated ID Type / Status
Subject TTC Davisville Carhouse E369420 entity
Predicate transitModeServed P31014 FINISHED
Object heavy rail rapid transit LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: heavy rail rapid transit | Statement: [TTC Davisville Carhouse, transitModeServed, heavy rail rapid transit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transitModeServed
Context triple: [TTC Davisville Carhouse, transitModeServed, heavy rail rapid transit]
  • A. publicTransitMode
    Indicates the type of public transportation (e.g., bus, train, subway) used or associated with a given trip or segment.
  • B. hasPublicTransitMode chosen
    Indicates that a location, route, or service is associated with or supports a specific mode of public transportation (e.g., bus, train, tram).
  • C. hasPublicTransitRole
    Indicates that an entity holds a specific functional role or responsibility within a public transit system.
  • D. hasPublicTransitServiceLevel
    Indicates the level or quality of public transit service provided to or available at a given location or entity.
  • E. hasTransitAccessTo
    Indicates that one place or entity is reachable from another via public or shared transportation services.
  • F. None of above.

Provenance (3 batches)

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_69d85a1849f48190bf898068b2806fae completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ec032548190840b558dde6057c7 completed April 16, 2026, 1:43 a.m.
PD Predicate disambiguation batch_69ded27f45548190a6d2b1b85cb47444 completed April 14, 2026, 11:49 p.m.
Created at: April 10, 2026, 3:20 a.m.