Triple
T28361716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köppen climate classification |
E718378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific classification system |
C33781
|
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: scientific classification system Context triple: [Köppen climate classification, instanceOf, scientific classification system]
-
A.
taxonomic system
A taxonomic system is an organized framework for classifying and naming entities—such as organisms, objects, or concepts—into hierarchical categories based on shared characteristics and relationships.
-
B.
plant classification system
A plant classification system is an organized framework that categorizes plants into hierarchical groups based on shared characteristics such as morphology, genetics, and evolutionary relationships.
-
C.
statistical classification system
A statistical classification system is a structured framework that organizes data, entities, or phenomena into predefined categories based on quantitative criteria and statistical methods to enable consistent analysis and comparison.
-
D.
angiosperm classification system
An angiosperm classification system is a structured framework used to organize and categorize flowering plants into hierarchical groups based on shared morphological, genetic, and evolutionary characteristics.
-
E.
ecoregion classification system
chosen
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.
- 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.