Triple

T318791
Position Surface form Disambiguated ID Type / Status
Subject America/Santiago E7766 entity
Predicate offsetFromUTCDSTSeconds P713 FINISHED
Object -10800 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: -10800 | Statement: [America/Santiago, offsetFromUTCDSTSeconds, -10800]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: offsetFromUTCDSTSeconds
Context triple: [America/Santiago, offsetFromUTCDSTSeconds, -10800]
  • A. offsetInSecondsFromUTC
    Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
  • B. offsetFromUTCInMinutes
    Indicates the number of minutes by which a given time value differs from Coordinated Universal Time (UTC), positive or negative.
  • C. offsetFromUTCInHours
    Indicates the number of hours a time value is offset from Coordinated Universal Time (UTC), positive for time zones ahead and negative for those behind.
  • D. offsetSeconds
    Indicates a temporal relationship where one event or time point occurs a specified number of seconds before or after another reference time.
  • E. UTCOffsetDaylightSavingTime chosen
    Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time 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_69a2e7e7af7881908890039d6be4e9b8 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eb7df63c8190b7cd1bcfdfd96187 completed Feb. 28, 2026, 1:19 p.m.
PD Predicate disambiguation batch_69a2e94513ec819089f5177f7a521e65 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.