Triple

T59605
Position Surface form Disambiguated ID Type / Status
Subject Chamorro Standard Time E1181 entity
Predicate coordinatedUniversalTimeRelation P712 FINISHED
Object UTC plus ten hours 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: UTC plus ten hours | Statement: [Chamorro Standard Time, coordinatedUniversalTimeRelation, UTC plus ten hours]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coordinatedUniversalTimeRelation
Context triple: [Chamorro Standard Time, coordinatedUniversalTimeRelation, UTC plus ten hours]
  • A. UTCOffsetDaylightSavingTime
    Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
  • B. UTCOffsetStandardTime chosen
    Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
  • C. observesDaylightSavingTime
    Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
  • D. typicalOffsetFromCentralTime
    Indicates the usual time difference between a given time zone and Central Time (CT), expressed as an offset in hours or minutes.
  • E. timeZoneHistorical
    Indicates that there is a historical time zone relationship, specifying how an entity’s time zone (including offsets, rules, or changes) applied during past periods.
  • 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_69a24a552ef88190a0df287d68c65cba completed Feb. 28, 2026, 1:52 a.m.
NER Named-entity recognition batch_69a250e401288190ba12322c9c5f07c9 completed Feb. 28, 2026, 2:20 a.m.
PD Predicate disambiguation batch_69a24e9f40908190a2f4a2111469b733 completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 1:55 a.m.