Triple
T34806713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kickapoo Traditional Council |
E1003378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tribal governing body |
C46277
|
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: tribal governing body Context triple: [Kickapoo Traditional Council, instanceOf, tribal governing body]
-
A.
tribal government committee
A tribal government committee is a formally organized group within a tribal nation’s governing structure that is responsible for reviewing, developing, and recommending policies, laws, and initiatives on specific issues affecting the tribe.
-
B.
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.
-
C.
First Nations tribal council
A First Nations tribal council is a governing body composed of representatives from one or more Indigenous communities that makes collective decisions on political, social, economic, and cultural matters affecting their people.
-
D.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
E.
Native American tribal council
chosen
A Native American tribal council is a governing body composed of elected or traditional leaders who make decisions, create policies, and oversee the welfare and cultural integrity of their tribe or nation.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.