Triple
T30377045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Cariban |
E772719
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subgroup of the 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 the Cariban languages Context triple: [Northern Cariban, instanceOf, subgroup of the Cariban languages]
-
A.
subgroup of Cariban languages
chosen
A subgroup of Cariban languages is a set of closely related languages within the Cariban family that share common historical origins, structural features, and lexical similarities distinguishing them from other Cariban branches.
-
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.
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.
-
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.
Native American languages subgroup
A Native American languages subgroup is a classification category that groups together related indigenous languages of the Americas based on shared historical origins, structural features, and linguistic evolution.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8 p.m.