Triple
T12676870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coahuila Kickapoo community |
E302836
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kickapoo community |
C24771
|
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: Kickapoo community Context triple: [Coahuila Kickapoo community, instanceOf, Kickapoo community]
-
A.
Kickapoo tribe
chosen
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.
-
B.
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.
-
C.
Sauk settlement
A Sauk settlement is a community or village established and inhabited by the Sauk (Sac) people, typically organized around kinship networks, seasonal subsistence activities, and cultural practices in their traditional homelands.
-
D.
Quileute tribal community
The Quileute tribal community is an Indigenous nation of the Pacific Northwest, centered in La Push, Washington, with a distinct language, culture, and governance rooted in ancestral ties to the land and waters of the Olympic Peninsula.
-
E.
Kalapuya band
A Kalapuya band is a local sociopolitical and kinship group of the Kalapuya people, traditionally occupying a specific territory in the Willamette Valley and surrounding regions of western Oregon.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:20 p.m.