Triple

T30291355
Position Surface form Disambiguated ID Type / Status
Subject Southern Ontario transportation network E770382 entity
Predicate includesTransitMode P31014 FINISHED
Object subway 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: subway | Statement: [Southern Ontario transportation network, includesTransitMode, subway]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesTransitMode
Context triple: [Southern Ontario transportation network, includesTransitMode, subway]
  • A. publicTransitMode
    Indicates the type of public transportation (e.g., bus, train, subway) used or associated with a given trip or segment.
  • B. hasTransitServiceType
    Indicates that a transit service is associated with a specific type or category of service (e.g., bus, rail, express).
  • C. appliesToTransportMode
    Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular mode of transport.
  • D. hasTransitAccessTo
    Indicates that one place or entity is reachable from another via public or shared transportation services.
  • E. 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).
  • 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_69f224875c288190a9b96b975006ec4a completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_6a0067cde0f08190b2cd93af5f00d519 completed May 10, 2026, 11:11 a.m.
PD Predicate disambiguation batch_6a0065820c8c8190994734433c64a30a completed May 10, 2026, 11:01 a.m.
Created at: April 29, 2026, 7:47 p.m.