Triple
T27617889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Hemisphere daylight saving times |
E700487
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | daylight saving time system |
C3001
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: daylight saving time system Context triple: [Southern Hemisphere daylight saving times, instanceOf, daylight saving time system]
-
A.
daylight saving time
chosen
Daylight saving time is a system of adjusting clocks forward or backward, typically by one hour, to extend evening daylight during warmer months and revert to standard time in colder months.
-
B.
daylight saving time period
A daylight saving time period is a recurring interval during which clocks are set forward from standard time to extend evening daylight, typically for energy conservation or lifestyle benefits.
-
C.
time zone reform
Time zone reform is the process of evaluating and changing how geographic regions are assigned to time zones or observe daylight saving, typically to improve social, economic, or political alignment with local timekeeping needs.
-
D.
time zone
A time zone is a geographically defined region that observes a uniform standard time, typically offset from Coordinated Universal Time (UTC), to synchronize clocks within that area.
-
E.
standard time zone
A standard time zone is a region of the Earth that observes a uniform official time, typically defined as an offset from Coordinated Universal Time (UTC), for legal, commercial, and social purposes.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 27, 2026, 2:13 p.m.