Triple
T35222366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wunambal language |
E1016993
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Australian language |
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: Western Australian language Context triple: [Wunambal language, instanceOf, Western Australian language]
-
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.
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.
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.
-
D.
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.
-
E.
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.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.