Triple
T30770122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacoh-Ta’Oih continuum |
E783499
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austroasiatic language group |
C8112
|
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: Austroasiatic language group Context triple: [Pacoh-Ta’Oih continuum, instanceOf, Austroasiatic language group]
-
A.
Austroasiatic language
An Austroasiatic language is a member of a large language family native to Southeast Asia and parts of South Asia, including languages such as Vietnamese, Khmer, and Mon.
-
B.
Austronesian language
An Austronesian language is any member of a large family of languages spoken from Madagascar across Island Southeast Asia and the Pacific to Easter Island, characterized by shared phonological, grammatical, and lexical features tracing back to a common ancestral tongue.
-
C.
branch of Austroasiatic languages
chosen
A branch of Austroasiatic languages is a subgroup within the Austroasiatic language family whose member languages share a common historical origin and distinctive linguistic features.
-
D.
Austroasiatic ethnic group
An Austroasiatic ethnic group is a community of people who share a common ancestry, culture, and language belonging to the Austroasiatic language family, primarily found in parts of South and Southeast Asia.
-
E.
Malayo-Polynesian language
A Malayo-Polynesian language is a member of a large branch of the Austronesian language family spoken across Southeast Asia, Madagascar, and the Pacific islands, characterized by shared phonological, grammatical, and lexical 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:40 p.m.