Triple
T20506879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daylight saving time (United States) |
E503457
|
entity |
| Predicate | usesTimeShift |
P69693
|
FINISHED |
| Object | one hour forward in spring |
—
|
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: one hour forward in spring | Statement: [Daylight saving time (United States), usesTimeShift, one hour forward in spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTimeShift Context triple: [Daylight saving time (United States), usesTimeShift, one hour forward in spring]
-
A.
timeShiftService
Indicates that a service is provided with a shifted or delayed time relative to its original or real-time schedule.
-
B.
usesInstantReplay
Indicates that an entity employs instant replay technology or review during an event, action, or decision process.
-
C.
timeShiftProperty
chosen
Indicates a relationship where one property value is derived from another by applying a temporal shift (e.g., offsetting it to an earlier or later point in time).
-
D.
usesTimeTravelFor
Indicates a relationship where an entity employs time travel as a means or method to achieve, affect, or interact with another entity or objective.
-
E.
supportsTimecodes
Indicates that one entity can handle, interpret, or work with timecode information associated with another entity or data stream.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dc82dd0819085d64d65a1e72c70 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:36 a.m.