Triple
T29792905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jinyun Mountain National Nature Reserve |
E756459
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mountainous protected area |
C10903
|
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: mountainous protected area Context triple: [Jinyun Mountain National Nature Reserve, instanceOf, mountainous protected area]
-
A.
high-mountain protected area
A high-mountain protected area is a designated conservation region in elevated, often rugged terrain that safeguards alpine ecosystems, biodiversity, and natural processes from significant human disturbance.
-
B.
protected area in the Alps
A protected area in the Alps is a legally designated mountain region managed to conserve its unique alpine ecosystems, landscapes, and biodiversity while regulating human activities such as tourism, grazing, and development.
-
C.
mountain region
A mountain region is a large geographic area characterized by elevated terrain, significant relief, and distinct climatic and ecological conditions associated with mountainous landscapes.
-
D.
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.
-
E.
mountain park
chosen
A mountain park is a protected natural area located in mountainous terrain, offering scenic landscapes, outdoor recreation, and conservation of local ecosystems and wildlife.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:13 p.m.