Triple
T30787399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Aslian languages |
E783991
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Aslian language subgroup |
C57224
|
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: Aslian language subgroup Context triple: [Northern Aslian languages, instanceOf, Aslian language subgroup]
-
A.
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.
-
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.
subgroup of Niger–Congo languages
A subgroup of Niger–Congo languages is a set of closely related languages within the Niger–Congo family that share a common ancestral origin and distinctive structural and lexical features.
-
D.
Austronesian subgroup
An Austronesian subgroup is a classification of related languages within the Austronesian language family that share common historical origins and linguistic features.
-
E.
Afroasiatic language branch
The Afroasiatic language branch is a major language family originating in the Middle East and North Africa, encompassing diverse languages such as Arabic, Hebrew, Amharic, and Hausa that share common historical and structural features.
- F. None of above. chosen
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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:41 p.m.