Triple
T750441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Time Zone |
E15434
|
entity |
| Predicate | DSTNotObservedIn |
P15037
|
FINISHED |
| Object | most of Saskatchewan |
—
|
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: most of Saskatchewan | Statement: [Central Time Zone, DSTNotObservedIn, most of Saskatchewan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DSTNotObservedIn Context triple: [Central Time Zone, DSTNotObservedIn, most of Saskatchewan]
-
A.
DSTobserved
Indicates that daylight saving time is in effect or being observed for a given time, date, or location.
-
B.
doesNotObserveDaylightSavingTimeIn
chosen
Indicates that a place or jurisdiction does not adjust its clocks for daylight saving time in the specified region or context.
-
C.
DSTseason
Indicates that the relationship specifies the daylight saving time (DST) period or season during which a time-related event or setting is in effect.
-
D.
DSTPolicy
Indicates a relationship where a timekeeping system follows a specific daylight saving time policy, defining how and when clocks are adjusted seasonally.
-
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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a5004f708190a984ee221716e19c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.