Triple

T100762
Position Surface form Disambiguated ID Type / Status
Subject Easter Island E2034 entity
Predicate timeZoneDSTOffset P713 FINISHED
Object UTC−5 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−5 | Statement: [Easter Island, timeZoneDSTOffset, UTC−5]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeZoneDSTOffset
Context triple: [Easter Island, timeZoneDSTOffset, UTC−5]
  • A. UTCOffsetDaylightSavingTime chosen
    Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
  • B. UTCOffsetStandardTime
    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. DSTAbbreviation
    Indicates that one entity is the standard abbreviated form used to represent another entity related to daylight saving time.
  • D. timeZoneType
    Indicates the classification or category of a time zone associated with an entity (e.g., standard, daylight, or specific time zone format/type).
  • E. typicalOffsetFromCentralTime
    Indicates the usual time difference between a given time zone and Central Time (CT), expressed as an offset in hours or minutes.
  • 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_69a24e0a5b7c81908d52da08c60dabc4 completed Feb. 28, 2026, 2:08 a.m.
NER Named-entity recognition batch_69a25760af348190bf402089c240887d completed Feb. 28, 2026, 2:48 a.m.
PD Predicate disambiguation batch_69a2563921f8819087f720b1c803579f completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:12 a.m.