Triple

T10032357
Position Surface form Disambiguated ID Type / Status
Subject Greenbank, Washington E204880 entity
Predicate hasUtcOffsetDST P713 FINISHED
Object UTC−07: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−07:00 | Statement: [Greenbank, Washington, hasUtcOffsetDST, UTC−07:00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUtcOffsetDST
Context triple: [Greenbank, Washington, hasUtcOffsetDST, UTC−07:00]
  • A. observesDSTOffset
    Indicates that one entity follows or applies a specific daylight saving time (DST) offset in its timekeeping or scheduling.
  • B. hasDSTComponent
    Indicates that something includes or is associated with a component related to Daylight Saving Time (DST) behavior or configuration.
  • C. hasStandardTimeUTCOffset
    Indicates the fixed difference in hours and minutes between an entity’s standard (non-daylight-saving) local time and Coordinated Universal Time (UTC).
  • D. 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.
  • 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_69ca834d77188190ad645e33e8ca3200 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cdce47845c8190ab5696267fdedcad completed April 2, 2026, 2:02 a.m.
PD Predicate disambiguation batch_69cd4b8638508190b22acc65500ec7d6 completed April 1, 2026, 4:44 p.m.
Created at: March 30, 2026, 8:54 p.m.