Triple
T14523631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kavango–Zambezi Transfrontier Conservation Area |
E340714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-border conservation area |
C7343
|
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: cross-border conservation area Context triple: [Kavango–Zambezi Transfrontier Conservation Area, instanceOf, cross-border conservation area]
-
A.
transboundary region
A transboundary region is a geographically contiguous area that spans across the borders of two or more political or administrative jurisdictions, sharing interconnected environmental, economic, social, or cultural systems.
-
B.
cross-border area
chosen
A cross-border area is a geographic region that spans across the boundaries of two or more countries, where social, economic, environmental, and political interactions occur and are often managed through cooperative arrangements.
-
C.
binational park
A binational park is a protected natural or recreational area that spans the border of two countries and is jointly managed or coordinated by both nations.
-
D.
network of protected areas
A network of protected areas is a coordinated system of geographically distinct conservation sites managed collectively to maintain biodiversity, ecological processes, and landscape connectivity.
-
E.
Protected area designation
A protected area designation is an official classification assigned to a geographic region to conserve its natural, cultural, or ecological values by regulating human activities and land use.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:22 a.m.