Triple
T36379061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puruborá languages |
E895991
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tupian language branch |
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 branch Context triple: [Puruborá languages, instanceOf, Tupian language branch]
-
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.
Oto-Manguean language branch
The Oto-Manguean language branch is a large and diverse family of indigenous Mesoamerican languages, primarily spoken in Mexico, known for complex tonal systems and significant internal variation.
-
C.
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.
-
D.
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.
-
E.
Yuman language branch
The Yuman language branch is a group of closely related Indigenous languages spoken primarily in the southwestern United States and northwestern Mexico, including parts of Arizona, California, and Baja California.
- 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.