Triple
T533519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahican language |
E12276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Algonquian 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: Eastern Algonquian language Context triple: [Mahican language, instanceOf, Eastern Algonquian 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.
Inuit language
Inuit language is a group of closely related Indigenous languages spoken across the Arctic regions of Alaska, Canada, and Greenland, characterized by polysynthetic word formation and rich expression of environmental and cultural concepts.
-
C.
Native American language
A Native American language is any of the indigenous languages historically and currently spoken by the Native peoples of the Americas, each embodying unique cultural knowledge, traditions, and worldviews.
-
D.
Uto-Aztecan language
A Uto-Aztecan language is a member of a Native American language family spoken from the western United States through northern and central Mexico, sharing common ancestral linguistic features despite diverse cultures and regions.
-
E.
American indigenous language
An American indigenous language is a native language originating from the Indigenous peoples of the Americas, encompassing diverse linguistic families and traditions that predate European colonization.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:32 p.m.