Triple

T35184876
Position Surface form Disambiguated ID Type / Status
Subject Gunwinyguan languages E1015958 entity
Predicate instanceOf P0 FINISHED
Object Indigenous Australian language family 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: Indigenous Australian language family
Context triple: [Gunwinyguan languages, instanceOf, Indigenous Australian language family]
  • A. 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.
  • B. 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.
  • C. indigenous North American language family
    A broad grouping of related indigenous languages spoken by Native peoples across North America, defined by shared historical origins and structural features.
  • D. Australian Aboriginal language community
    An Australian Aboriginal language community is a group of Aboriginal people connected by shared traditional language, cultural practices, and ancestral ties to specific Country within Australia.
  • E. 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.
  • 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_69f76ddd815c8190b822eea06630f9fb completed May 3, 2026, 3:46 p.m.
Created at: May 3, 2026, 4:02 p.m.