Triple
T10883681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Time |
E256985
|
entity |
| Predicate | observesDSTEndRule |
P718
|
FINISHED |
| Object | first Sunday in November |
—
|
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: first Sunday in November | Statement: [Alaska Time, observesDSTEndRule, first Sunday in November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observesDSTEndRule Context triple: [Alaska Time, observesDSTEndRule, first Sunday in November]
-
A.
DSTEndRule
chosen
Indicates the rule or condition that specifies when daylight saving time ends in a given timekeeping system.
-
B.
observesDSTOffset
Indicates that one entity follows or applies a specific daylight saving time (DST) offset in its timekeeping or scheduling.
-
C.
DSTobserved
Indicates that daylight saving time is in effect or being observed for a given time, date, or location.
-
D.
DSTObservedInCountry
Indicates that daylight saving time (DST) is implemented or observed within a given country.
-
E.
DSTStartRule
Indicates the rule or condition that determines when daylight saving time begins for a given time zone or region.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751dc3518819090e03d81ea5c8aa9 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.