Triple

T37235729
Position Surface form Disambiguated ID Type / Status
Subject Manitoba–Saskatchewan border E923566 entity
Predicate hasAdjacentTimeZoneOnManitobaSide P196848 FINISHED
Object Central Time Zone NE NERFINISHED

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: Central Time Zone | Statement: [Manitoba–Saskatchewan border, hasAdjacentTimeZoneOnManitobaSide, Central Time Zone]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAdjacentTimeZoneOnManitobaSide
Context triple: [Manitoba–Saskatchewan border, hasAdjacentTimeZoneOnManitobaSide, Central Time Zone]
  • A. timeZoneCanadianSide
    Indicates that the referenced entity is located in the Canadian part of a region and uses the time zone defined for that Canadian side.
  • B. adjacentToCanadianProvince
    Indicates that one entity is directly next to or shares a border with a Canadian province.
  • C. hasTimeZoneDifferenceAlongBorder
    Indicates that two adjacent regions share a border across which their official time zones differ.
  • D. isNeighboringTimeZoneTo
    Indicates that two time zones are directly adjacent to each other, typically sharing a common boundary or differing by one standard time offset step.
  • E. adjacentTimeZoneWest
    Indicates that one time zone is directly to the west of another, sharing a common boundary without any other time zone in between.
  • F. None of above. chosen

Provenance (4 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_69f76ea9fee88190a589f661d95a7189 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fe6b7c785c8190aaab06019f571434 completed May 8, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69fe68edef20819081c77f9607b944dd completed May 8, 2026, 10:51 p.m.
PDg Predicate description generation batch_69fe6b7a823881909dc2037fe25bea24 completed May 8, 2026, 11:02 p.m.
Created at: May 3, 2026, 4:15 p.m.