Triple

T32452249
Position Surface form Disambiguated ID Type / Status
Subject Kooskia, Idaho E829322 entity
Predicate timeZoneNote P85469 FINISHED
Object city is near the boundary between Pacific and Mountain time zones 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: city is near the boundary between Pacific and Mountain time zones | Statement: [Kooskia, Idaho, timeZoneNote, city is near the boundary between Pacific and Mountain time zones]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeZoneNote
Context triple: [Kooskia, Idaho, timeZoneNote, city is near the boundary between Pacific and Mountain time zones]
  • A. hasTimeZoneNote chosen
    Indicates that there is an associated note or annotation providing additional information or clarification about a time zone.
  • B. timeZoneState
    Indicates that one entity is a state or region associated with the time zone of another entity.
  • C. timeZoneChange
    Indicates a change in the time zone associated with an entity, such as shifting from one time offset or region-based time standard to another.
  • D. timeZoneDependence
    Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
  • E. timeZoneContext
    Indicates the time zone setting or context in which an event, action, or relationship is interpreted.
  • 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_69f3491df9288190afc0b23b1d6e72ce completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6cd126fcc8190aa1f1f146e45ec0c completed May 3, 2026, 4:20 a.m.
PD Predicate disambiguation batch_69f6cc1470808190b70cdfd7a6395670 completed May 3, 2026, 4:16 a.m.
Created at: May 1, 2026, 12:56 a.m.