Triple
T28013263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neutral (Attawandaron) variety |
E707476
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iroquoian language variety |
C53667
|
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: Iroquoian language variety Context triple: [Neutral (Attawandaron) variety, instanceOf, Iroquoian language variety]
-
A.
Algonquian language
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.
Iroquoian-speaking people
Iroquoian-speaking people are Indigenous groups of North America historically united by related Iroquoian languages, shared cultural practices, and complex political systems, primarily located in the Great Lakes, St. Lawrence River, and Appalachian regions.
-
C.
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.
-
D.
Chinookan language variety
A Chinookan language variety is a specific form or dialect of the Chinookan language family traditionally spoken by Indigenous Chinookan peoples of the Pacific Northwest, characterized by its own phonological, grammatical, and lexical features.
-
E.
Amerindian language
An Amerindian language is any of the indigenous languages spoken by the native peoples of the Americas, encompassing a diverse range of distinct linguistic families and traditions.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 8:05 p.m.