Triple
T5528837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | October |
E144994
|
entity |
| Predicate | hasDaylightSavingTimeChangeIn |
P15036
|
FINISHED |
| Object | many Northern Hemisphere countries |
—
|
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: many Northern Hemisphere countries | Statement: [October, hasDaylightSavingTimeChangeIn, many Northern Hemisphere countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDaylightSavingTimeChangeIn Context triple: [October, hasDaylightSavingTimeChangeIn, many Northern Hemisphere countries]
-
A.
hasDaylightSavingVariant
Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
-
B.
isDaylightSavingShift
chosen
Indicates that a change in local clock time occurs due to the start or end of daylight saving time.
-
C.
isDaylightSavingTime
Indicates that the specified time or date falls within a period when daylight saving time rules are in effect.
-
D.
DSTOffsetChange
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
E.
observesDaylightSavingTime
Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f8b6c348190b7d414dc1907d09a |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.