Triple
T14404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Time Zone |
E288
|
entity |
| Predicate | UTCOffsetStandardTime |
P712
|
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: [Eastern Time Zone, UTCOffsetStandardTime, UTC−05:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UTCOffsetStandardTime Context triple: [Eastern Time Zone, UTCOffsetStandardTime, UTC−05:00]
-
A.
observesDaylightSavingTime
Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
-
B.
locatedInTimeZone
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
C.
locale
Indicates that one entity is the place, setting, or geographic area in which another entity exists, occurs, or is situated.
-
D.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- F. None of above. chosen
Provenance (4 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a240b249788190af8dbf7e80e9c91b |
completed | Feb. 28, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69a23feae8c481908d8c50faac01fc5c |
completed | Feb. 28, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69a240b1551c81908abcae128ea45d00 |
completed | Feb. 28, 2026, 1:11 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.