Triple
T1220076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake County, Indiana |
E26198
|
entity |
| Predicate | followsTimeZoneDST |
P384
|
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: [Lake County, Indiana, followsTimeZoneDST, UTC−05:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsTimeZoneDST Context triple: [Lake County, Indiana, followsTimeZoneDST, UTC−05:00]
-
A.
followedByTimeZone
Indicates that one time zone chronologically succeeds another in a defined ordering or sequence.
-
B.
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.
-
C.
daylightSavingTimeHemisphere
Indicates the hemisphere (e.g., northern or southern) in which a location follows a particular daylight saving time pattern.
-
D.
observesDaylightSavingTime
chosen
Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
-
E.
observesDaylightSavingWith
Indicates that one entity follows the same daylight saving time rules or schedule as another entity.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be1ead088190bf44dc6ab1edf18b |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.