Triple

T17202117
Position Surface form Disambiguated ID Type / Status
Subject Munda–Nicobarese branch E417500 entity
Predicate instanceOf P0 FINISHED
Object proposed branch of Austroasiatic 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: proposed branch of Austroasiatic
Context triple: [Munda–Nicobarese branch, instanceOf, proposed branch of Austroasiatic]
  • A. 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.
  • 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. Austronesian subgroup
    An Austronesian subgroup is a classification of related languages within the Austronesian language family that share common historical origins and linguistic 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 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.
  • 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_69d886d6ba8c819093215917b3d01689 completed April 10, 2026, 5:12 a.m.
Created at: April 10, 2026, 5:38 a.m.