Triple

T4481515
Position Surface form Disambiguated ID Type / Status
Subject America/Edmonton E100144 entity
Predicate utcOffsetStandardTime P712 FINISHED
Object UTC−07:00 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: UTC−07:00 | Statement: [America/Edmonton, utcOffsetStandardTime, UTC−07:00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: utcOffsetStandardTime
Context triple: [America/Edmonton, utcOffsetStandardTime, UTC−07:00]
  • A. UTCOffsetStandardTime chosen
    Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
  • B. UTCOffsetDaylightSavingTime
    Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
  • C. utcOffsetDescription
    Indicates the textual description of how far a time zone’s local time differs from Coordinated Universal Time (UTC), often including details like hours, minutes, and daylight saving adjustments.
  • D. typicalOffsetFromCentralTime
    Indicates the usual time difference between a given time zone and Central Time (CT), expressed as an offset in hours or minutes.
  • E. timeOffsetType
    Indicates the type or category of temporal offset that specifies how one time point is shifted relative to another.
  • 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_69b34553cbe48190afa8ac1cac285b86 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35728ed508190ba0e882fa62d8848 completed March 13, 2026, 12:15 a.m.
PD Predicate disambiguation batch_69b3563d63008190816e37027e761375 completed March 13, 2026, 12:11 a.m.
Created at: March 12, 2026, 11:36 p.m.