Triple

T20747719
Position Surface form Disambiguated ID Type / Status
Subject British Columbia Highway 91 E510629 entity
Predicate isCommuterRoute P3916 FINISHED
Object yes 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: yes | Statement: [British Columbia Highway 91, isCommuterRoute, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isCommuterRoute
Context triple: [British Columbia Highway 91, isCommuterRoute, yes]
  • A. isPublicTransportRoute
    Indicates that a given route is designated and operated as part of a public transportation system available for general use.
  • B. isCommuterHub
    Indicates that a location functions as a central node where many commuters start, end, or transfer during their regular travel.
  • C. hasCommuterOrientation chosen
    Indicates that an entity is designed or intended primarily for use by commuters, emphasizing suitability for regular travel between home and work or study.
  • D. hasCommuterTraffic
    Indicates that there is regular, recurring traffic flow associated with people traveling between their homes and places of work or study.
  • E. hasCommuterPattern
    Indicates that there is a characteristic or recurring pattern in how an entity regularly travels between locations, typically for work or daily activities.
  • 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_69e0b4c845e88190b4c5f3ae79291182 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c226fbf881909794eff3ee9e206b completed April 21, 2026, 12:17 a.m.
PD Predicate disambiguation batch_69e5c0509608819080cdbf47fcddfe36 completed April 20, 2026, 5:57 a.m.
Created at: April 16, 2026, 12:33 p.m.