Triple
T13871141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Rosa Indian Reservation |
E333451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federally recognized Indian 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: federally recognized Indian reservation Context triple: [Santa Rosa Indian Reservation, instanceOf, federally recognized Indian 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.
federally recognized tribe
A federally recognized tribe is a Native American or Alaska Native governing body that the U.S. federal government formally acknowledges as a sovereign political entity with a government-to-government relationship and eligibility for specific legal rights, services, and protections.
-
C.
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.
-
D.
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.
-
E.
tribal nation
A tribal nation is a sovereign Indigenous community recognized as a distinct political and cultural entity with its own government, territory, and traditions.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:14 p.m.