Triple
T15745297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Havasupai Tribal Council |
E381707
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Native American tribal government body |
C4075
|
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: Native American tribal government body Context triple: [Havasupai Tribal Council, instanceOf, Native American tribal government body]
-
A.
tribal government agency
chosen
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.
-
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.
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.
Alaska Native organization
An Alaska Native organization is an entity established by or for Alaska Native peoples to represent their interests, manage resources, provide services, and promote cultural, social, and economic well-being within Alaska Native communities.
-
E.
tribal confederation
A tribal confederation is a loose alliance of distinct tribes that cooperate for mutual defense, governance, or shared interests while retaining their individual identities and autonomy.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.