Triple
T36241068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramarama languages |
E891518
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tupian languages 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 languages subgroup Context triple: [Ramarama languages, instanceOf, Tupian languages subgroup]
-
A.
Tupian languages
Tupian languages are a family of indigenous languages of South America, primarily spoken in Brazil and neighboring regions, known for their significant internal diversity and historical importance in pre-colonial and colonial communication.
-
B.
Palaungic language subgroup
The Palaungic language subgroup is a branch of the Austroasiatic language family comprising several closely related languages spoken primarily by Palaung and related ethnic groups in Myanmar, China, Laos, and neighboring regions.
-
C.
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.
-
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.
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.
- 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.