Triple

T37295947
Position Surface form Disambiguated ID Type / Status
Subject Wangurri E925802 entity
Predicate instanceOf P0 FINISHED
Object Yolŋu language variety C62798 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: Yolŋu language variety
Context triple: [Wangurri, instanceOf, Yolŋu language variety]
  • A. 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.
  • B. Tiwi language variety
    A Tiwi language variety is a specific form or dialect of the Tiwi language spoken by the Tiwi people of Australia, characterized by its unique phonological, grammatical, and lexical features within the broader Tiwi linguistic tradition.
  • C. Kunama language variety
    A Kunama language variety is a specific regional or social form of the Kunama language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Kunama linguistic continuum.
  • D. Yana language variety
    Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
  • E. Miriwoongic language
    The Miriwoongic language is a small family of closely related Indigenous Australian languages spoken traditionally by the Miriwoong and neighboring peoples of the eastern Kimberley region in Western Australia and the Northern Territory.
  • F. None of above. chosen

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_69f76eb0f86c819098dee07393e69ec3 completed May 3, 2026, 3:50 p.m.
Created at: May 3, 2026, 4:16 p.m.