Triple
T6892472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pama–Nyungan languages |
E159080
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Aboriginal language family |
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: Australian Aboriginal language family Context triple: [Pama–Nyungan languages, instanceOf, Australian Aboriginal language family]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Malayo-Polynesian language
A Malayo-Polynesian language is a member of a large branch of the Austronesian language family spoken across Southeast Asia, Madagascar, and the Pacific islands, characterized by shared phonological, grammatical, 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:24 p.m.