Triple
T2651702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Yuma Indian Reservation |
E53913
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federally recognized tribal land |
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 tribal land Context triple: [Fort Yuma Indian Reservation, instanceOf, federally recognized tribal land]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
federal territory
A federal territory is a geographic area under the direct jurisdiction and administration of a federal government, distinct from constituent states or provinces and typically lacking the same degree of self-governance.
-
E.
tribal government agency
A tribal government agency is an administrative body established by a Native American or Indigenous tribe to manage governmental functions, deliver services, and implement policies on behalf of the tribal community.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:53 p.m.