Triple

T30804432
Position Surface form Disambiguated ID Type / Status
Subject Lyck E784458 entity
Predicate timezoneDSTPresentDayLocation P9475 FINISHED
Object Central European Summer Time 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 European Summer Time | Statement: [Lyck, timezoneDSTPresentDayLocation, Central European Summer Time]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timezoneDSTPresentDayLocation
Context triple: [Lyck, timezoneDSTPresentDayLocation, Central European Summer Time]
  • A. DSTTimeZone chosen
    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.
  • B. locatedInTimeZoneUTCOffsetDST
    Indicates that an entity exists or operates in a time zone that observes daylight saving time with a specified UTC offset during that DST period.
  • C. hasDSTOfCountry
    Indicates that a country observes a particular daylight saving time (DST) scheme or rule.
  • D. DSTAlternativePreviouslyUsedUTCOffset
    Indicates that a daylight saving time alternative has, at some point in the past, used a specific UTC offset.
  • E. DSTObservedInCountry
    Indicates that daylight saving time (DST) is implemented or observed within a given country.
  • 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_69f224b3a7ec819096939414d103e31e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6a0ea04888190ac3a813b603bcb5c completed May 3, 2026, 1:12 a.m.
PD Predicate disambiguation batch_69f69fe463248190aa78128abeab1183 completed May 3, 2026, 1:07 a.m.
Created at: April 29, 2026, 8:42 p.m.