Triple

T750422
Position Surface form Disambiguated ID Type / Status
Subject Central Time Zone E15434 entity
Predicate timeInWinter P18772 FINISHED
Object six hours behind Coordinated Universal Time 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: six hours behind Coordinated Universal Time | Statement: [Central Time Zone, timeInWinter, six hours behind Coordinated Universal Time]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeInWinter
Context triple: [Central Time Zone, timeInWinter, six hours behind Coordinated Universal Time]
  • A. differenceFromLondonTimeInWinter
    Indicates the time difference between a given location’s local time and London’s local time during the winter season.
  • B. timeDifferenceToCETWinter
    Indicates the time offset between a given time and Central European Time during the winter (standard time) period.
  • C. summerWinterCycle
    Indicates a recurring transition between summer and winter seasons, capturing the cyclical change in conditions or states across these two periods.
  • D. summerTimeZone
    Indicates that a specified region or entity uses a particular time zone during the summer or daylight-saving period.
  • E. hasNoSeasonalClockChanges
    Indicates that a place or system does not adjust its clocks for seasonal time changes such as daylight saving time.
  • 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_69a493599a0081908da65f3407af1ef2 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a64adf2c81908e48090be35dd9d9 completed March 1, 2026, 8:49 p.m.
PD Predicate disambiguation batch_69a4a5004f708190a984ee221716e19c completed March 1, 2026, 8:43 p.m.
PDg Predicate description generation batch_69a4a58c0a84819094f07658dc651b36 completed March 1, 2026, 8:46 p.m.
Created at: March 1, 2026, 7:37 p.m.