Triple

T27030622
Position Surface form Disambiguated ID Type / Status
Subject Yuin-Kuric subgroup E680907 entity
Predicate instanceOf P0 FINISHED
Object branch of Pama–Nyungan languages C49370 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: branch of Pama–Nyungan languages
Context triple: [Yuin-Kuric subgroup, instanceOf, branch of Pama–Nyungan languages]
  • A. Pama–Nyungan language
    A Pama–Nyungan language is a member of the largest and most widespread family of Indigenous Australian languages, covering most of the Australian continent and sharing common structural and lexical features.
  • B. Australian Aboriginal language subgroup chosen
    An Australian Aboriginal language subgroup is a classification category that groups together closely related Indigenous Australian languages based on shared linguistic features and common historical origins.
  • C. 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.
  • D. Noongar language variety
    A Noongar language variety is a specific regional or dialectal form of the Noongar Aboriginal language spoken in southwestern Western Australia, characterized by distinct phonological, lexical, and grammatical features within the broader Noongar language continuum.
  • 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_69eeeb5566f08190813daf896fa3da04 completed April 27, 2026, 4:51 a.m.
Created at: April 27, 2026, 7:13 a.m.