Triple
T32277506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ojo Caliente Reservation |
E824593
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Apache reservation |
C4323
|
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: Apache reservation Context triple: [Ojo Caliente Reservation, instanceOf, Apache reservation]
-
A.
Indian reservation
chosen
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.
-
B.
tribal reserve
A tribal reserve is a designated area of land set aside by a government for the use, residence, and self-governance of an Indigenous tribe or tribes, often recognized as their traditional territory.
-
C.
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.
-
D.
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.
-
E.
Aboriginal reserve
An Aboriginal reserve is a tract of land set aside by a government for the use and occupation of Indigenous peoples, typically recognized as a distinct community with certain self-governing rights and cultural protections.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:43 a.m.