Triple
T30095138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paraguay Summer Time |
E764843
|
entity |
| Predicate | timeShiftDirection |
P61649
|
FINISHED |
| Object | clock advanced 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: clock advanced one hour | Statement: [Paraguay Summer Time, timeShiftDirection, clock advanced one hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeShiftDirection Context triple: [Paraguay Summer Time, timeShiftDirection, clock advanced one hour]
-
A.
timeShiftProperty
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).
-
B.
timeShiftService
Indicates that a service is provided with a shifted or delayed time relative to its original or real-time schedule.
-
C.
timeTravelDirection
chosen
Indicates the temporal direction in which time travel occurs, such as moving into the past or into the future.
-
D.
timeJump
Indicates a discontinuous transition of an entity from one point in time to another, skipping the intervening duration.
-
E.
clockChangeDirection
Indicates a change in the rotational or movement direction of a clock or clock-like mechanism.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 7:07 p.m.