Triple
T29630311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Cariban |
E755553
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subgroup of Cariban languages |
C55986
|
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: subgroup of Cariban languages Context triple: [Southern Cariban, instanceOf, subgroup of Cariban languages]
-
A.
subgroup of Mayan languages
A subgroup of Mayan languages is a set of closely related Mayan languages that share a common ancestral branch within the Mayan language family, characterized by shared phonological, grammatical, and lexical innovations.
-
B.
subfamily of Tupian languages
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.
-
C.
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.
-
D.
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.
-
E.
Cariban language
A Cariban language is a member of the Cariban family of indigenous languages spoken primarily in northern South America, known for their complex verb morphology and diverse phonological systems.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
Created at: April 28, 2026, 6:40 p.m.