Triple

T19616969
Position Surface form Disambiguated ID Type / Status
Subject Wyoming, Pennsylvania E470886 entity
Predicate isInTimeZoneDSTUTCOffset P74117 FINISHED
Object UTC−04: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−04:00 | Statement: [Wyoming, Pennsylvania, isInTimeZoneDSTUTCOffset, UTC−04:00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInTimeZoneDSTUTCOffset
Context triple: [Wyoming, Pennsylvania, isInTimeZoneDSTUTCOffset, UTC−04:00]
  • A. isInTimeZoneOffset
    Indicates that one temporal entity occurs within, or is associated with, a specific time zone offset relative to a reference time standard (such as UTC).
  • B. DSTIsAheadOfUTC
    Indicates that the time in a region observing Daylight Saving Time is ahead of Coordinated Universal Time (UTC) by a specified offset.
  • C. locatedInTimeZoneUTCOffsetDST chosen
    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. observesDSTOffset
    Indicates that one entity follows or applies a specific daylight saving time (DST) offset in its timekeeping or scheduling.
  • E. isDaylightSavingTime
    Indicates that the specified time or date falls within a period when daylight saving time rules are in effect.
  • 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_69d8e510fa248190b7afb274a1d4cf73 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e640e272808190800c5bccccd64753 completed April 20, 2026, 3:06 p.m.
PD Predicate disambiguation batch_69e514e5cb108190ae260e466c447314 completed April 19, 2026, 5:46 p.m.
Created at: April 10, 2026, 1:43 p.m.