Triple
T9925504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRDT |
E187911
|
entity |
| Predicate | typeOfClockChange |
P8057
|
FINISHED |
| Object | clocks advanced by one 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 advanced by one hour | Statement: [IRDT, typeOfClockChange, clocks advanced by one hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfClockChange Context triple: [IRDT, typeOfClockChange, clocks advanced by one hour]
-
A.
DSTChangeReason
Indicates the reason or cause for a change in daylight saving time status or rules.
-
B.
DSTOffsetChange
chosen
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
C.
typicalDSTChangeHour
Indicates the usual clock time at which a daylight saving time change (such as shifting clocks forward or backward) is applied.
-
D.
clockChangeDirection
Indicates a change in the rotational or movement direction of a clock or clock-like mechanism.
-
E.
timeZoneType
Indicates the classification or category of a time zone associated with an entity (e.g., standard, daylight, or specific time zone format/type).
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb599e32c8190ac676fa89c131bb6 |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.