Triple
T26539028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacred Forest of Kpassè |
E671331
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected woodland |
C14730
|
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 woodland Context triple: [Sacred Forest of Kpassè, instanceOf, protected woodland]
-
A.
protected landscape area
A protected landscape area is a designated region where the interaction of people and nature over time has produced a distinct character with significant ecological, cultural, and scenic value that is conserved and managed through legal or other effective means.
-
B.
woodland site
chosen
A woodland site is a defined area of land predominantly covered by trees and undergrowth, managed or recognized for its ecological, recreational, or conservation value.
-
C.
reserve forest
A reserve forest is a legally protected woodland area where human activities like logging, grazing, and land conversion are restricted or regulated to conserve biodiversity and natural resources.
-
D.
forest preserve district
A forest preserve district is a governmental or quasi-governmental entity responsible for acquiring, managing, and protecting natural areas and open space—often forests, prairies, wetlands, and related habitats—for conservation, recreation, and education.
-
E.
protected natural area system
A protected natural area system is an organized network of geographically defined spaces managed through legal or other effective means to conserve biodiversity, ecosystem services, and natural or cultural values over the long term.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:40 a.m.