Triple
T4481518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Edmonton |
E100144
|
entity |
| Predicate | daylightSavingTimeStartRule |
P717
|
FINISHED |
| Object | second Sunday in March |
—
|
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: second Sunday in March | Statement: [America/Edmonton, daylightSavingTimeStartRule, second Sunday in March]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: daylightSavingTimeStartRule Context triple: [America/Edmonton, daylightSavingTimeStartRule, second Sunday in March]
-
A.
daylightSavingRule
Indicates the rule or policy that defines when and how daylight saving time is applied or adjusted for a given context.
-
B.
DSTStartRule
chosen
Indicates the rule or condition that determines when daylight saving time begins for a given time zone or region.
-
C.
DSTEndRule
Indicates the rule or condition that specifies when daylight saving time ends in a given timekeeping system.
-
D.
DSTChangeReason
Indicates the reason or cause for a change in daylight saving time status or rules.
-
E.
DSTPolicy
Indicates a relationship where a timekeeping system follows a specific daylight saving time policy, defining how and when clocks are adjusted seasonally.
- 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:36 p.m.