Triple
T13053232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azores Time |
E327497
|
entity |
| Predicate | DSTClockChangeAutumn |
P59379
|
FINISHED |
| Object | clocks go back 1 hour |
—
|
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: clocks go back 1 hour | Statement: [Azores Time, DSTClockChangeAutumn, clocks go back 1 hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DSTClockChangeAutumn Context triple: [Azores Time, DSTClockChangeAutumn, clocks go back 1 hour]
-
A.
DSTChangeDirectionInAutumn
chosen
Indicates the direction (e.g., forward or backward) in which clocks are adjusted when daylight saving time ends in autumn.
-
B.
DSTChangeYear
Indicates the specific year in which a daylight saving time (DST) change occurs or is scheduled to occur.
-
C.
DSTOffsetChange
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
D.
DSTStartRule
Indicates the rule or condition that determines when daylight saving time begins for a given time zone or region.
-
E.
DSTEndRule
Indicates the rule or condition that specifies when daylight saving time ends in a given timekeeping system.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:58 p.m.