Triple
T6334322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-Oceanic language |
E142453
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austronesian proto-language |
C967
|
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: Austronesian proto-language Context triple: [Proto-Oceanic language, instanceOf, Austronesian proto-language]
-
A.
Austronesian language
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Tai-Kadai language
A Tai-Kadai language is a member of a family of tonal languages spoken primarily in Southeast Asia and southern China, characterized by similar phonological, lexical, and grammatical features that suggest a common historical origin.
-
E.
Austronesian subgroup
An Austronesian subgroup is a classification of related languages within the Austronesian language family that share common historical origins and 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:30 p.m.