Triple
T32184401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dos-teh-seh |
E822067
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chiricahua Apache person |
C19454
|
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: Chiricahua Apache person Context triple: [Dos-teh-seh, instanceOf, Chiricahua Apache person]
-
A.
Chiricahua Apache
chosen
Chiricahua Apache refers to a group of Apachean people historically based in the southwestern United States and northern Mexico, known for their distinct culture, language, and resistance to colonization.
-
B.
Jicarilla Apache people
The Jicarilla Apache people are a Native American tribe of the Southern Athabaskan language family, traditionally inhabiting areas of northern New Mexico and southern Colorado, known for their rich ceremonial traditions, basketry, and contemporary governance on the Jicarilla Apache Nation reservation.
-
C.
Western Apache group
A Western Apache group is a regional social and cultural subdivision of the Apache peoples of the American Southwest, sharing closely related language varieties, kinship ties, and traditional lifeways within a specific territory.
-
D.
O’odham people
The O’odham people are an Indigenous group of the Sonoran Desert region of the U.S. Southwest and northern Mexico, encompassing several related communities with shared O’odham languages, cultural traditions, and ancestral ties to the land.
-
E.
Ho-Chunk person
A Ho-Chunk person is an individual who belongs to the Ho-Chunk Nation, an Indigenous people of the North American Midwest with a distinct language, culture, and history.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:35 a.m.