Triple
T32311470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shakopee Mdewakanton Sioux Community |
E825510
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dakota tribe |
C58149
|
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: Dakota tribe Context triple: [Shakopee Mdewakanton Sioux Community, instanceOf, Dakota tribe]
-
A.
Oglala Lakota
The Oglala Lakota are one of the seven bands of the Lakota people, a Native American nation of the Great Plains known for their rich cultural traditions, historical resistance to U.S. expansion, and ongoing efforts to preserve their language and sovereignty.
-
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.
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.
-
D.
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.
-
E.
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.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:46 a.m.