Triple
T32496357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaurishankar Conservation Area |
E830534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected area of Nepal |
C61556
|
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: protected area of Nepal Context triple: [Gaurishankar Conservation Area, instanceOf, protected area of Nepal]
-
A.
region of Nepal
A region of Nepal is a geographically defined area within the country characterized by shared administrative boundaries, cultural traits, economic activities, and environmental features.
-
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.
region of Bhutan
A region of Bhutan is a geographically defined area within the country characterized by shared administrative governance, cultural traits, and environmental features.
-
D.
protected area in Mongolia
A protected area in Mongolia is a legally designated geographic region set aside to conserve the country’s unique ecosystems, wildlife, and cultural landscapes, while regulating human activities to ensure long-term environmental sustainability.
-
E.
protected area of British Columbia
A protected area of British Columbia is a designated geographic region set aside by the province to conserve natural ecosystems, wildlife, and cultural values while often providing opportunities for low-impact recreation and education.
- F. None of above. chosen
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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:59 a.m.