Triple
T11303296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amedzofe dialect |
E267650
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Ewe language |
C29517
|
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 Ewe language Context triple: [Amedzofe dialect, instanceOf, variety of Ewe language]
-
A.
variety of the Nuer language
A variety of the Nuer language is a distinct regional or social form of Nuer characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other Nuer 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 Tongan language
A variety of Tongan language is a distinct form or dialect of Tongan characterized by unique phonological, lexical, or grammatical features associated with a particular region, community, or social group.
-
D.
Yana language variety
Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
-
E.
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.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:32 p.m.