Triple
T13928699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IST |
E334928
|
entity |
| Predicate | daylightSavingTimeAppliesInSeason |
P15746
|
FINISHED |
| Object | summer |
—
|
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: summer | Statement: [IST, daylightSavingTimeAppliesInSeason, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: daylightSavingTimeAppliesInSeason Context triple: [IST, daylightSavingTimeAppliesInSeason, summer]
-
A.
isDaylightSavingTime
Indicates that the specified time or date falls within a period when daylight saving time rules are in effect.
-
B.
isDaylightSavingShift
Indicates that a change in local clock time occurs due to the start or end of daylight saving time.
-
C.
DSTseason
chosen
Indicates that the relationship specifies the daylight saving time (DST) period or season during which a time-related event or setting is in effect.
-
D.
daylightSavingTimeHemisphere
Indicates the hemisphere (e.g., northern or southern) in which a location follows a particular daylight saving time pattern.
-
E.
hasTimeZoneInWinter
Indicates that an entity is associated with a specific time zone during the winter season.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa900a0819095eeb1bc46b0336e |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.