Triple

T5818587
Position Surface form Disambiguated ID Type / Status
Subject CST (Cuba) E129047 entity
Predicate DSTOffsetDifferenceFromStandard P44984 FINISHED
Object +1 hour 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: +1 hour | Statement: [CST (Cuba), DSTOffsetDifferenceFromStandard, +1 hour]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: DSTOffsetDifferenceFromStandard
Context triple: [CST (Cuba), DSTOffsetDifferenceFromStandard, +1 hour]
  • A. DSTComparedToStandardTime
    Indicates that a time value is expressed relative to standard time, specifying whether and how it is adjusted for Daylight Saving Time.
  • B. DSTOffsetType chosen
    Indicates the relationship between a time reference and the amount of time it is shifted from standard time due to daylight saving time adjustments.
  • C. DSTOffsetChange
    Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
  • D. DSTTimeZone
    Indicates that a time-related entity operates under a daylight saving time rule or belongs to a time zone that observes daylight saving time adjustments.
  • E. differenceFromUSEasternDaylightTime
    Indicates that one temporal value differs by a specified amount or offset from the time expressed in US Eastern Daylight Time.
  • 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_69c0084869e881908d7859492183ca7b completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0400f1af881908d376ea4793f6dea completed March 22, 2026, 7:16 p.m.
PD Predicate disambiguation batch_69c0333fdd7081908d829265caa2ac11 completed March 22, 2026, 6:21 p.m.
Created at: March 22, 2026, 3:53 p.m.