Triple
T23925568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goundam dialect of Koyra Chiini |
E602341
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Koyra Chiini |
C48220
|
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: regional variety of Koyra Chiini Context triple: [Goundam dialect of Koyra Chiini, instanceOf, regional variety of Koyra Chiini]
-
A.
regional variety of Ghomalaʼ
A regional variety of Ghomalaʼ is a geographically localized dialect of the Ghomalaʼ language characterized by distinct phonological, lexical, or syntactic features specific to a particular area or community.
-
B.
Kaqchikel language variety
The Kaqchikel language variety is a Mayan language spoken primarily in the central highlands of Guatemala, characterized by its agglutinative morphology, ergative-absolutive alignment, and rich system of aspect and status markers.
-
C.
Luri language variety
A Luri language variety is a specific regional or social form of the Luri language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader continuum of Southwestern Iranian dialects.
-
D.
regional variety of Ghomalaʼ language
A regional variety of the Ghomalaʼ language is a geographically or socially distinct form of Ghomalaʼ characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar from other Ghomalaʼ varieties.
-
E.
Cora language variety
Cora language variety refers to any distinct regional, social, or dialectal form of the Cora language as used by different Cora-speaking communities.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 8:44 p.m.