Triple
T13079072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherokee Nation Executive Branch |
E307135
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of tribal government |
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: component of tribal government Context triple: [Cherokee Nation Executive Branch, instanceOf, component of tribal government]
-
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.
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.
-
C.
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.
-
D.
branch of government
A branch of government is a major division of a state's governing system, such as the executive, legislative, or judicial branch, each with distinct powers and responsibilities designed to balance and limit authority.
-
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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
Created at: April 9, 2026, 9:01 p.m.