Triple
T21803199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Andean dry puna ecoregion |
E538286
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | puna ecoregion |
C4265
|
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: puna ecoregion Context triple: [Central Andean dry puna ecoregion, instanceOf, puna ecoregion]
-
A.
Andean ecosystem
An Andean ecosystem is a high-altitude mountain environment along the Andes characterized by steep climatic gradients, unique flora and fauna adapted to thin air and cold temperatures, and complex interactions between glaciers, grasslands, forests, and human communities.
-
B.
Andean mountain protected area
An Andean mountain protected area is a designated conservation region within the Andes that safeguards high-altitude ecosystems, endemic biodiversity, and cultural landscapes while regulating human activities to ensure long-term ecological integrity.
-
C.
Andean national park
An Andean national park is a protected natural area located within the Andes mountain range, established to conserve its unique high-altitude ecosystems, biodiversity, and cultural heritage while enabling regulated public enjoyment and research.
-
D.
alpine region
chosen
An alpine region is a high-altitude mountainous area characterized by rugged terrain, cold climates, and specialized plant and animal life adapted to harsh environmental conditions.
-
E.
tropical rainforest
A tropical rainforest is a dense, biodiverse forest ecosystem found near the equator, characterized by high rainfall, warm temperatures year-round, and multiple layers of vegetation.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:53 p.m.