Triple
T463882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Summer Time |
E8401
|
entity |
| Predicate | clockChange |
P8057
|
FINISHED |
| Object | clocks set forward 1 hour at start |
—
|
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 at start | Statement: [British Summer Time, clockChange, clocks set forward 1 hour at start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clockChange Context triple: [British Summer Time, clockChange, clocks set forward 1 hour at start]
-
A.
clockChangeDirectionAtStart
Indicates that the direction of a clock’s movement changes at the beginning of a specified interval or event.
-
B.
clockChangeDirectionAtEnd
Indicates that the direction of a clock-related process or movement is reversed or altered at its endpoint or completion.
-
C.
DSTOffsetChange
chosen
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
D.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
E.
DSTChangeYear
Indicates the specific year in which a daylight saving time (DST) change occurs or is scheduled to occur.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efc214788190a8dff20fec4412e0 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edea1acc81908a72d9f4c43438ea |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.