Triple
T29545867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi Choctaw |
E749628
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Choctaw |
C55882
|
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: regional variety of Choctaw Context triple: [Mississippi Choctaw, instanceOf, regional variety of Choctaw]
-
A.
Kickapoo language variety
A Kickapoo language variety is a specific dialect or form of the Kickapoo language, distinguished by its unique phonological, lexical, and grammatical features used by particular Kickapoo-speaking communities.
-
B.
Chatino language variety
A Chatino language variety is a specific regional or social form of the Chatino language, characterized by its own distinct phonological, lexical, and grammatical features within the broader Chatino linguistic continuum.
-
C.
Southern Athabaskan language
A Southern Athabaskan language is a member of the Athabaskan branch of the Na-Dené language family spoken primarily in the Southwestern United States and northern Mexico, characterized by complex verb morphology and tonal or pitch-accent features.
-
D.
Cherokee
Cherokee: A Native American people originally from the southeastern United States, known for their rich cultural traditions, complex social and political structures, and resilience through forced removal and adaptation.
-
E.
Otomi language variety
An Otomi language variety is a specific regional or social form of the Otomi language, distinguished by its own phonological, lexical, and grammatical features within the broader Otomi linguistic continuum.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:07 p.m.