Triple
T346312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chile Summer Time |
E6949
|
entity |
| Predicate | typicalClockChangeAmount |
P8057
|
FINISHED |
| Object | 60 minutes |
—
|
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: 60 minutes | Statement: [Chile Summer Time, typicalClockChangeAmount, 60 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClockChangeAmount Context triple: [Chile Summer Time, typicalClockChangeAmount, 60 minutes]
-
A.
DSTOffsetChange
chosen
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
B.
DSTChangeReason
Indicates the reason or cause for a change in daylight saving time status or rules.
-
C.
DSTChangeYear
Indicates the specific year in which a daylight saving time (DST) change occurs or is scheduled to occur.
-
D.
typicalOffsetFromCentralTime
Indicates the usual time difference between a given time zone and Central Time (CT), expressed as an offset in hours or minutes.
-
E.
typicalOffsetFromPacificTime
Indicates the usual time difference between a given time zone and Pacific Time (PT), without accounting for temporary variations like daylight saving changes.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb0240e88190bc70784772f5fa30 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95451a4819090f4e4fb9b21a493 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.