Triple
T34325500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Arrernte |
E880855
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arandic language |
C60165
|
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: Arandic language Context triple: [Lower Arrernte, instanceOf, Arandic language]
-
A.
Andic language
An Andic language is a member of a small subgroup of the Northeast Caucasian language family spoken primarily in the western part of Dagestan, Russia, characterized by complex phonology and rich morphological systems.
-
B.
Katuic language
A Katuic language is a member of a subgroup of the Austroasiatic language family spoken primarily by Katuic ethnic groups in Laos, Vietnam, and neighboring regions, characterized by complex phonologies and rich systems of verbal morphology.
-
C.
Batanic language
The Batanic language is a subgroup of Austronesian languages spoken primarily in the Batanes Islands of the northern Philippines and nearby areas, characterized by shared phonological and lexical features distinct from neighboring Philippine languages.
-
D.
Kaduic language
Kaduic language is a hypothetical or fictional linguistic system characterized by its unique phonology, grammar, and vocabulary associated with the conceptual culture or species called Kaduic.
-
E.
Korandje language
The Korandje language is a highly endangered Northern Songhay language spoken by a small community in the oasis town of Tabelbala in southwestern Algeria, notable for its extensive contact-induced influences from Berber and Arabic.
- 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:58 a.m.