Triple
T20880149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hays, Texas |
E514122
|
entity |
| Predicate | locatedInTimeZoneOffsetUTC |
P109
|
FINISHED |
| Object | UTC−06: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−06:00 | Statement: [Hays, Texas, locatedInTimeZoneOffsetUTC, UTC−06:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTimeZoneOffsetUTC Context triple: [Hays, Texas, locatedInTimeZoneOffsetUTC, 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
chosen
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
C.
locatedInUtmZone
Indicates that something is situated within a specific Universal Transverse Mercator (UTM) coordinate zone.
-
D.
isLocatedInTimeZoneRegion
Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
-
E.
partlyLocatedInTimeZone
Indicates that an entity’s extent overlaps multiple time zones, with at least part of it falling within the specified time zone.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67974348190bd3484032c0d7b31 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.