Triple
T21512211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWh |
E530754
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Köppen climate classification code |
C21403
|
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: Köppen climate classification code Context triple: [BWh, instanceOf, Köppen climate classification code]
-
A.
Köppen climate classification
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
chosen
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.
standardized climate modeling input
A standardized climate modeling input is a consistently formatted, quality-controlled dataset or parameter set designed to ensure comparability, reproducibility, and interoperability across different climate models and simulations.
-
E.
public land classification
Public land classification is the systematic categorization of government-owned lands based on their designated uses, protections, and management objectives, such as conservation, recreation, resource extraction, or development.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:25 p.m.