Triple
T4156006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicobarese languages |
E91415
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austroasiatic languages |
C2793
|
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 languages Context triple: [Nicobarese languages, instanceOf, Austroasiatic languages]
-
A.
Austroasiatic language
chosen
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.
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.
Sino-Tibetan language
A Sino-Tibetan language is any member of a large language family, including Chinese and Tibeto-Burman languages, characterized by shared historical origins in East and Southeast Asia and often featuring tonal systems and analytic grammar.
-
E.
branch of Austroasiatic languages
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.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:44 p.m.