Triple
T27010981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pisba páramo |
E680382
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-altitude Andean moorland |
C13059
|
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: high-altitude Andean moorland Context triple: [Pisba páramo, instanceOf, high-altitude Andean moorland]
-
A.
Andean ecosystem
chosen
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
An Andean mountain is a high, often snow-capped peak within the Andes range, characterized by steep relief, active tectonics, and diverse ecological zones that vary dramatically with altitude.
-
C.
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.
-
D.
alpine region
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.
Andean mountain range
The Andean mountain range is a vast, continuous chain of high mountains along the western edge of South America, characterized by towering peaks, active volcanoes, diverse ecosystems, and rich cultural history.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 7:03 a.m.