Triple
T24478631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kpase |
E617301
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Fon language |
C49056
|
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 Fon language Context triple: [Kpase, instanceOf, variety of Fon language]
-
A.
variety of Fang language
A variety of Fang language is a specific regional or social form of the Fang language distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Fang forms.
-
B.
Songhay language variety
A Songhay language variety is a specific regional or social form of the Songhay language continuum, distinguished by its unique phonological, lexical, and grammatical features while remaining mutually intelligible to varying degrees with other Songhay varieties.
-
C.
variety of the Kaili language
A variety of the Kaili language is a distinct regional or social form of Kaili characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Kaili forms.
-
D.
variety of the Duala language
A variety of the Duala language is a regional or social form of Duala distinguished by specific phonological, lexical, or grammatical features while remaining mutually intelligible with other Duala forms.
-
E.
variety of the Berom language
A variety of the Berom language is a distinct regional or social form of Berom characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:21 a.m.