Triple
T28361715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köppen climate classification |
E718378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | climate classification system |
C21404
|
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: climate classification system Context triple: [Köppen climate classification, instanceOf, climate classification system]
-
A.
Köppen climate classification
chosen
The Köppen climate classification is a widely used system that categorizes the world's climates based on average temperature and precipitation patterns, grouping regions into distinct climate types such as tropical, arid, temperate, continental, and polar.
-
B.
climate type
A climate type is a classification of a region’s long-term weather patterns, defined by characteristic ranges of temperature, precipitation, and seasonal variation.
-
C.
ecoregion classification system
An ecoregion classification system is a structured framework that categorizes geographic areas into distinct ecological regions based on shared environmental conditions, ecosystems, and biodiversity patterns.
-
D.
environmental classification
Environmental classification is the systematic categorization of environments or environmental conditions based on their physical, biological, chemical, or socio-economic characteristics to support analysis, management, and decision-making.
-
E.
climate system
The climate system is the interconnected set of components—including the atmosphere, oceans, land surface, cryosphere, and biosphere—that together determine Earth’s long-term weather patterns and energy balance.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 12:52 a.m.