Triple
T34676996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AKDT |
E890517
|
entity |
| Predicate | replacedByOutsideDST |
P195368
|
FINISHED |
| Object | Alaska Standard Time |
—
|
NE NERFINISHED |
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: Alaska Standard Time | Statement: [AKDT, replacedByOutsideDST, Alaska Standard Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByOutsideDST Context triple: [AKDT, replacedByOutsideDST, Alaska Standard Time]
-
A.
DSTNotRegularSince
Indicates that daylight saving time has not been regularly observed in the specified location since a given point in time.
-
B.
DSTOffsetChange
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
C.
usesDSTNotationChange
Indicates that a system or context applies a change in notation or representation when switching between standard time and daylight saving time.
-
D.
DSTChangeReason
Indicates the reason or cause for a change in daylight saving time status or rules.
-
E.
previouslyObservedDST
Indicates that the subject has been observed in a context where daylight saving time (DST) was in effect at some point in the past.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: May 1, 2026, 2:05 a.m.