Triple

T1177855
Position Surface form Disambiguated ID Type / Status
Subject Atlantic Time Zone E25068 entity
Predicate observesDaylightSavingTimeInSomeRegions P26276 FINISHED
Object true 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: true | Statement: [Atlantic Time Zone, observesDaylightSavingTimeInSomeRegions, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: observesDaylightSavingTimeInSomeRegions
Context triple: [Atlantic Time Zone, observesDaylightSavingTimeInSomeRegions, true]
  • A. observesDaylightSavingTime
    Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
  • B. observesDaylightSavingWith
    Indicates that one entity follows the same daylight saving time rules or schedule as another entity.
  • C. hasDaylightSavingVariant
    Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
  • D. doesNotObserveDaylightSavingTimeIn
    Indicates that a place or jurisdiction does not adjust its clocks for daylight saving time in the specified region or context.
  • E. daylightSavingTimeHemisphere
    Indicates the hemisphere (e.g., northern or southern) in which a location follows a particular daylight saving time pattern.
  • 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_69a494267b4c819088c97a59182bf56a completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bd53e4b48190abb2167f8074a6bc completed March 1, 2026, 10:27 p.m.
PD Predicate disambiguation batch_69a4bb5844348190b01ac6506906ba3b completed March 1, 2026, 10:19 p.m.
PDg Predicate description generation batch_69a4bd52177081908c5cec8e731b836e completed March 1, 2026, 10:27 p.m.
Created at: March 1, 2026, 7:45 p.m.