Triple
T11594359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pitjantjatjara language |
E274963
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Desert language |
C30294
|
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 Desert language Context triple: [Pitjantjatjara language, instanceOf, Western Desert language]
-
A.
Saharan language
A Saharan language is a member of a small family of related languages spoken primarily in the central Sahara region of Africa, characterized by shared grammatical structures and vocabulary distinct from neighboring language families.
-
B.
ancient North Arabian dialect
An ancient North Arabian dialect is a historical variety of the North Arabian branch of the Semitic languages, attested in inscriptions and texts from pre-Islamic northern Arabia.
-
C.
South Arabian language
A South Arabian language is a member of a group of Semitic languages historically spoken in the southern Arabian Peninsula, characterized by distinct phonological, morphological, and script traditions separate from other Arabic varieties.
-
D.
Northern Berber language
A Northern Berber language is a member of the Berber branch of the Afroasiatic language family spoken primarily across the northern regions of North Africa, characterized by shared phonological, morphological, and syntactic features distinct from other Berber varieties.
-
E.
Berber language
Berber language is a branch of the Afroasiatic language family comprising several closely related languages spoken by the indigenous Amazigh peoples of North Africa.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:38 p.m.