Triple
T12724773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Francis-Sokoki dialect |
E304074
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Western Abenaki language |
C1356
|
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: variety of Western Abenaki language Context triple: [St. Francis-Sokoki dialect, instanceOf, variety of Western Abenaki language]
-
A.
Algonquian language
chosen
An Algonquian language is any member of a family of Indigenous languages of North America, historically spoken from the Atlantic coast to the Great Plains and characterized by complex morphology and polysynthetic structure.
-
B.
Southern Wakashan language
A Southern Wakashan language is a member of the southern branch of the Wakashan language family, traditionally spoken by Indigenous peoples of the Pacific Northwest Coast, particularly on Vancouver Island and adjacent mainland areas.
-
C.
Yavapai language variety
A Yavapai language variety is a specific form or dialect of the Yavapai language, distinguished by unique phonological, lexical, or grammatical features used by a particular Yavapai-speaking community.
-
D.
Yana language variety
Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
-
E.
Muskogean language
A Muskogean language is any member of a family of Native American languages originally spoken in the southeastern United States, including Creek, Choctaw, Chickasaw, and related tongues.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:25 p.m.