Triple

T26324895
Position Surface form Disambiguated ID Type / Status
Subject NZCI E662223 entity
Predicate associatedTimeZoneOffsetDST P713 FINISHED
Object UTC+13:45 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+13:45 | Statement: [NZCI, associatedTimeZoneOffsetDST, UTC+13:45]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedTimeZoneOffsetDST
Context triple: [NZCI, associatedTimeZoneOffsetDST, UTC+13:45]
  • A. timeZoneOffsetDestination
    Indicates the time difference (offset from a reference time, typically UTC) that applies to the destination location in a temporal or travel-related context.
  • B. UTCOffsetDaylightSavingTime chosen
    Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
  • C. 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.
  • D. timeZoneOriginDST
    Indicates that the relationship specifies the original time zone of an entity, including whether daylight saving time (DST) is in effect.
  • E. DSTOffsetType
    Indicates the relationship between a time reference and the amount of time it is shifted from standard time due to daylight saving time adjustments.
  • 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_69ee812f32748190871d970c4e2a8ddf completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69ff136ed2a881908f713401083970d1 completed May 9, 2026, 10:58 a.m.
PD Predicate disambiguation batch_69ff10f9e3448190b6cb6ea5a67713c1 completed May 9, 2026, 10:48 a.m.
Created at: April 26, 2026, 10:30 p.m.