Triple

T1177814
Position Surface form Disambiguated ID Type / Status
Subject Atlantic Time Zone E25068 entity
Predicate UTCOffsetDaylightTime P713 FINISHED
Object UTC−03:00 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−03:00 | Statement: [Atlantic Time Zone, UTCOffsetDaylightTime, UTC−03:00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: UTCOffsetDaylightTime
Context triple: [Atlantic Time Zone, UTCOffsetDaylightTime, UTC−03:00]
  • 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. daylightSavingTimeHemisphere
    Indicates the hemisphere (e.g., northern or southern) in which a location follows a particular daylight saving time pattern.
  • D. differenceFromUSEasternDaylightTime
    Indicates that one temporal value differs by a specified amount or offset from the time expressed in US Eastern Daylight Time.
  • E. timeOffsetType
    Indicates the type or category of temporal offset that specifies how one time point is shifted relative to another.
  • 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_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.
Created at: March 1, 2026, 7:45 p.m.