Triple
T37047420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toende Kusaal |
E916955
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Kusaal language |
C64845
|
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: variety of Kusaal language Context triple: [Toende Kusaal, instanceOf, variety of Kusaal language]
-
A.
variety of Koshali language
A variety of Koshali language is a regional or social form of Koshali distinguished by systematic differences in pronunciation, vocabulary, and grammar used by a particular community.
-
B.
variety of the Katu language
A variety of the Katu language is a distinct regional or social form of Katu characterized by systematic differences in pronunciation, vocabulary, and/or grammar while remaining mutually intelligible with other Katu forms.
-
C.
variety of Kunama language
A variety of Kunama language is a distinct regional or social form of the Kunama language characterized by unique phonological, lexical, or grammatical features within the broader Kunama-speaking community.
-
D.
variety of Kalasha language
A variety of the Kalasha language is a distinct regional or social form of Kalasha characterized by systematic differences in pronunciation, vocabulary, and/or grammar within the broader Kalasha-speaking community.
-
E.
variety of the Kati language
A variety of the Kati language is a distinct regional or social form of Kati characterized by its own systematic differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other Kati forms.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.