Triple
T22303696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gadjang |
E551320
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Aboriginal Australian language |
C2571
|
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: Aboriginal Australian language Context triple: [Gadjang, instanceOf, Aboriginal Australian language]
-
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.
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.
Aboriginal Australian
An Aboriginal Australian is a member of the Indigenous peoples of the Australian continent, belonging to diverse cultural and linguistic groups with deep ancestral connections to the land and rich traditions spanning tens of thousands of years.
-
D.
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.
-
E.
Indigenous language
chosen
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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:41 p.m.