Triple

T35182790
Position Surface form Disambiguated ID Type / Status
Subject Maung E1015897 entity
Predicate instanceOf P0 FINISHED
Object indigenous language of Australia C21827 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: indigenous language of Australia
Context triple: [Maung, instanceOf, indigenous language of Australia]
  • A. Australian Aboriginal language subgroup
    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.
  • B. Tasmanian Aboriginal language
    A Tasmanian Aboriginal language is any of the now-extinct indigenous languages once spoken by the Aboriginal peoples of Tasmania, characterized by diverse dialects and limited surviving documentation.
  • C. traditional Indigenous Australian language area
    A traditional Indigenous Australian language area is a geographically and culturally defined region in which a particular Aboriginal or Torres Strait Islander language (or closely related dialects) is historically spoken and maintained by its associated community.
  • D. Pama–Nyungan language chosen
    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.
  • E. Indigenous language
    An Indigenous language is a native tongue traditionally spoken by the original inhabitants of a region, embodying their cultural knowledge, identity, and worldview.
  • 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_69f76ddcc108819097f96853b7ed9ef4 completed May 3, 2026, 3:46 p.m.
Created at: May 3, 2026, 4:02 p.m.