Triple
T32045363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Tribe of Kansas and Nebraska |
E818331
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ioway tribe |
C57627
|
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: Ioway tribe Context triple: [Iowa Tribe of Kansas and Nebraska, instanceOf, Ioway tribe]
-
A.
Nisenan tribe
The Nisenan tribe is a Native American people indigenous to the California Sierra Nevada foothills and Sacramento Valley, known for their distinct language, cultural traditions, and deep connection to their ancestral lands.
-
B.
Kickapoo tribe
The Kickapoo tribe is a Native American people originally from the Great Lakes region, known for their resistance to displacement, semi-nomadic lifestyle, and communities now located in Oklahoma, Kansas, Texas, and Mexico.
-
C.
Ho-Chunk tribe
The Ho-Chunk tribe is a Native American nation originally from the Wisconsin and Illinois regions, known for its distinct Siouan language, rich cultural traditions, and enduring sovereignty.
-
D.
Chippewa tribe
The Chippewa tribe, also known as the Ojibwe or Anishinaabe, is a Native American people traditionally inhabiting the Great Lakes region, known for their rich oral traditions, intricate beadwork, and enduring cultural and political presence across the United States and Canada.
-
E.
Miwok tribe
The Miwok tribe is a group of Native American peoples indigenous to central California, traditionally living in the Sierra Nevada foothills, Central Valley, and surrounding regions, with distinct languages, cultures, and customs tied closely to the local environment.
- F. None of above. chosen
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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:20 a.m.