Triple
T25112982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talamanca Cabécar Indigenous Reserve |
E629047
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | indigenous reserve |
C21045
|
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: indigenous reserve Context triple: [Talamanca Cabécar Indigenous Reserve, instanceOf, indigenous reserve]
-
A.
Indian reserve
An Indian reserve is a tract of land set aside under federal authority for the use and benefit of a specific First Nations community, typically governed by band leadership and subject to distinct legal and administrative frameworks.
-
B.
First Nations reserve
A First Nations reserve is a tract of land set aside under the Indian Act and treaty agreements for the use and benefit of a specific First Nations community, typically governed by that community’s band council.
-
C.
Indian reservation
An Indian reservation is a tract of land managed by a Native American tribe under the U.S. Bureau of Indian Affairs, where the tribe exercises certain sovereign rights and self-governance.
-
D.
indigenous territory
chosen
An indigenous territory is a geographically defined area traditionally inhabited, used, or managed by an Indigenous people, where they maintain cultural, spiritual, social, and often legal relationships to the land and its resources.
-
E.
public reserved land
Public reserved land is a designated area owned or controlled by a government entity and legally set aside for specific public purposes such as conservation, recreation, infrastructure, or future community use, restricting private development and exploitation.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:27 a.m.