Triple
T11293365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palawa kani |
E267385
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tasmanian Aboriginal language |
C29501
|
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: Tasmanian Aboriginal language Context triple: [Palawa kani, instanceOf, Tasmanian Aboriginal 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.
Miwok language
The Miwok language is a group of closely related Native American languages traditionally spoken by the Miwok peoples of central California, known for their rich verb morphology and diverse dialects.
-
C.
Great Andamanese language
The Great Andamanese language is an endangered mixed language spoken by the indigenous Great Andamanese people of the Andaman Islands, combining elements from several original Andamanese languages with influences from Hindi and other contact languages.
-
D.
Papuan language
A Papuan language is any of the numerous non-Austronesian, non-Australian indigenous languages spoken primarily on the island of New Guinea and neighboring regions, representing several distinct and often unrelated language families.
-
E.
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.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:32 p.m.