Triple
T7680168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuin–Kuric languages |
E173970
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subgroup of Australian Aboriginal languages |
C21827
|
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 Australian Aboriginal languages Context triple: [Yuin–Kuric languages, instanceOf, subgroup of Australian Aboriginal languages]
-
A.
Pama–Nyungan language
chosen
A Pama–Nyungan language is a member of the largest and most widespread family of Indigenous Australian languages, covering most of the Australian continent and sharing common structural and lexical features.
-
B.
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.
-
C.
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.
-
D.
Papuan language
A Papuan language is any of the numerous non-Austronesian, non-Australian indigenous languages spoken primarily on the island of New Guinea and neighboring regions, representing several distinct and often unrelated language families.
-
E.
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.
- 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4:01 p.m.