Triple
T24091893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arikem |
E596806
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | primary subgroup of the Tupian language family |
C20190
|
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: primary subgroup of the Tupian language family Context triple: [Arikem, instanceOf, primary subgroup of the Tupian language family]
-
A.
subfamily of Tupian languages
chosen
A subfamily of Tupian languages is a smaller, genetically related group of languages within the larger Tupian family that share a more recent common ancestor and distinctive linguistic features.
-
B.
Oto-Manguean language
An Oto-Manguean language is a member of a large, diverse family of indigenous Mesoamerican languages, primarily spoken in Mexico, characterized by complex tonal systems and significant grammatical and phonological variation.
-
C.
branch of the Chibchan language family
A branch of the Chibchan language family is a subgroup of related Chibchan languages that share a common ancestral origin and distinctive linguistic features within the broader family.
-
D.
Munda languages subgroup
The Munda languages subgroup is a branch of the Austroasiatic language family spoken primarily in eastern and central India, characterized by agglutinative morphology and distinctive phonological and syntactic features.
-
E.
Penutian languages subgroup
The Penutian languages subgroup is a proposed family of Native American languages, primarily spoken in western North America, that are hypothesized to share a common ancestral origin based on structural and lexical similarities.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 10:53 p.m.