Triple
T5339366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year Without a Summer |
E123906
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | climatic anomaly |
C3904
|
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: climatic anomaly Context triple: [Year Without a Summer, instanceOf, climatic anomaly]
-
A.
climate phenomenon
chosen
A climate phenomenon is a recurring or notable pattern or event in the Earth’s climate system, such as El Niño or monsoon cycles, that significantly influences weather and environmental conditions over large regions and timescales.
-
B.
Holocene climatic anomaly
The Holocene climatic anomaly is a period of relatively warm and variable climate conditions occurring roughly between 4,000 and 2,500 years ago during the Holocene epoch, marked by regional shifts in temperature and precipitation patterns.
-
C.
climatic period
A climatic period is a distinct interval of time characterized by relatively stable and identifiable climate conditions, such as temperature and precipitation patterns, that differ from those of preceding and succeeding intervals.
-
D.
atmospheric feature
An atmospheric feature is any distinguishable structure, pattern, or phenomenon within a planet’s atmosphere, such as clouds, storms, or jet streams, that arises from atmospheric dynamics and composition.
-
E.
atmospheric–oceanic oscillation
An atmospheric–oceanic oscillation is a large-scale, recurring pattern of coupled variations in the atmosphere and ocean that influences climate and weather over seasonal to multidecadal timescales.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2 p.m.