Triple
T12020571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farallones de Cali National Natural Park |
E286138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national park of Colombia |
C6039
|
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: national park of Colombia Context triple: [Farallones de Cali National Natural Park, instanceOf, national park of Colombia]
-
A.
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.
-
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.
sector of Tijuca National Park
A sector of Tijuca National Park is a defined management and geographic subdivision of the park, characterized by specific natural features, conservation objectives, and permitted public uses.
-
D.
national park area
chosen
A national park area is a protected geographic region designated by a government to conserve natural landscapes, ecosystems, and wildlife while providing opportunities for public recreation and education.
-
E.
province of Colombia
A province of Colombia is an intermediate territorial subdivision within a department, grouping several municipalities for administrative, planning, and coordination purposes.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.