Triple

T38320065
Position Surface form Disambiguated ID Type / Status
Subject Wilder, Minnesota E1036638 entity
Predicate locatedInTimeZoneUTCOffsetStandard GENERATED
Object UTC−06:00 UNRECOGNIZED GENERATED

How this triple was built (1 step)

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.

PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInTimeZoneUTCOffsetStandard
Context triple: [Wilder, Minnesota, locatedInTimeZoneUTCOffsetStandard, UTC−06:00]
  • A. locatedInTimeZoneUTCOffsetDST
    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.
  • B. locatedInTimeZone
    Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
  • C. isLocatedInTimeZoneRegion
    Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
  • D. UTCOffsetStandardTime chosen
    Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
  • E. locatedInUtmZone
    Indicates that something is situated within a specific Universal Transverse Mercator (UTM) coordinate zone.
  • F. None of above.

Provenance (1 batch)

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_69f76e1c16fc8190bde982289dd5106b completed May 3, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:30 p.m.