Triple
T4909274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain Daylight Time |
E110191
|
entity |
| Predicate | DSTChangeDirectionInSpring |
P8057
|
FINISHED |
| Object | clocks set forward 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 set forward 1 hour | Statement: [Mountain Daylight Time, DSTChangeDirectionInSpring, clocks set forward 1 hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DSTChangeDirectionInSpring Context triple: [Mountain Daylight Time, DSTChangeDirectionInSpring, clocks set forward 1 hour]
-
A.
DSTChangeYear
Indicates the specific year in which a daylight saving time (DST) change occurs or is scheduled to occur.
-
B.
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.
-
C.
DSTStartRule
Indicates the rule or condition that determines when daylight saving time begins for a given time zone or region.
-
D.
DSTChangeReason
Indicates the reason or cause for a change in daylight saving time status or rules.
-
E.
DSTOffsetChange
chosen
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e99414081908c3d3283f563bba4 |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.