Triple

T1439446
Position Surface form Disambiguated ID Type / Status
Subject Cedarville, Illinois, United States E31035 entity
Predicate hasTimeZoneUTCOffsetDST P713 FINISHED
Object UTC−05: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−05:00 | Statement: [Cedarville, Illinois, United States, hasTimeZoneUTCOffsetDST, UTC−05:00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTimeZoneUTCOffsetDST
Context triple: [Cedarville, Illinois, United States, hasTimeZoneUTCOffsetDST, UTC−05:00]
  • A. UTCOffsetDaylightSavingTime chosen
    Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
  • B. usesUTCOffset
    Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
  • C. hasTimeZones
    Indicates that an entity is associated with one or more time zones in which it is valid or operates.
  • D. hasDaylightSavingVariant
    Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
  • E. DSTTimeZone
    Indicates that a time-related entity operates under a daylight saving time rule or belongs to a time zone that observes 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_69a4991633388190a4d61b5a98aa407a completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c5ff8dbc81909eafcfc9f2260a22 completed March 1, 2026, 11:04 p.m.
PD Predicate disambiguation batch_69a4c478f65481909ee716791c663491 completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8 p.m.