Triple
T4344331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Annular Mode variability |
E97862
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | atmospheric circulation pattern |
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: atmospheric circulation pattern Context triple: [Southern Annular Mode variability, instanceOf, atmospheric circulation pattern]
-
A.
atmospheric general circulation model
An atmospheric general circulation model is a complex numerical model that simulates the three-dimensional, large-scale movement of air and energy in Earth’s atmosphere to study and predict climate and weather patterns.
-
B.
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.
-
C.
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.
-
D.
regional wind
A regional wind is a persistent or recurring air movement pattern that is characteristic of and largely confined to a specific geographic area, influenced by local topography, land–sea contrasts, and regional climate conditions.
-
E.
katabatic wind
A katabatic wind is a gravity-driven downslope wind that occurs when dense, cold air flows from higher elevations to lower areas, often producing strong, gusty conditions in valleys and coastal regions.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:15 p.m.