Triple
T24091989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramarama |
E596808
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tupian language subgroup |
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: Tupian language subgroup Context triple: [Ramarama, instanceOf, Tupian language subgroup]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Yuman language subgroup
The Yuman language subgroup is a branch of the Yuman–Cochimí language family comprising closely related Indigenous languages spoken primarily along the lower Colorado River, in southwestern Arizona, southeastern California, and northern Baja California.
-
E.
Bantoid languages
Bantoid languages are a branch of the Benue–Congo family within the Niger–Congo language phylum, comprising Bantu and closely related non-Bantu languages spoken primarily in Central and West Africa.
- 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.