Triple

T26979326
Position Surface form Disambiguated ID Type / Status
Subject Mountain Standard Time (no DST) E679551 entity
Predicate typicalClockChangePolicy P120174 FINISHED
Object no clock changes throughout the year 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: no clock changes throughout the year | Statement: [Mountain Standard Time (no DST), typicalClockChangePolicy, no clock changes throughout the year]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalClockChangePolicy
Context triple: [Mountain Standard Time (no DST), typicalClockChangePolicy, no clock changes throughout the year]
  • A. typicalDSTChangeHour
    Indicates the usual clock time at which a daylight saving time change (such as shifting clocks forward or backward) is applied.
  • B. DSTTransitionPolicy chosen
    Indicates how a system or process handles the change in timekeeping rules when entering or exiting daylight saving time.
  • C. DSTPolicy
    Indicates a relationship where a timekeeping system follows a specific daylight saving time policy, defining how and when clocks are adjusted seasonally.
  • D. DSTOffsetChange
    Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
  • E. DSTChangeReason
    Indicates the reason or cause for a change in daylight saving time status or rules.
  • 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_69eeeb507a7081909d516e1fa08b7d29 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69ff397e19a88190a945b826159f5290 completed May 9, 2026, 1:41 p.m.
PD Predicate disambiguation batch_69ff392400d0819088d30d08d4a774bd completed May 9, 2026, 1:39 p.m.
Created at: April 27, 2026, 6:44 a.m.