Triple
T27617892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Hemisphere daylight saving times |
E700487
|
entity |
| Predicate | typicalShift |
P201210
|
FINISHED |
| Object | UTC+1 relative to standard time |
—
|
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: UTC+1 relative to standard time | Statement: [Southern Hemisphere daylight saving times, typicalShift, UTC+1 relative to standard time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalShift Context triple: [Southern Hemisphere daylight saving times, typicalShift, UTC+1 relative to standard time]
-
A.
shiftsWhen
Indicates that one state, condition, or configuration changes to another under specified circumstances or triggers.
-
B.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
C.
typicalDSTChangeHour
Indicates the usual clock time at which a daylight saving time change (such as shifting clocks forward or backward) is applied.
-
D.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
E.
typicalOffsetRange
Indicates the usual or expected range of positional or temporal deviation between related elements.
- F. None of above. chosen
Provenance (4 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
| PDg | Predicate description generation | batch_69ffdf46e18c8190a5e4f4e5211cb087 |
completed | May 10, 2026, 1:28 a.m. |
Created at: April 27, 2026, 2:13 p.m.