Triple
T3619933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yafiʿi Arabic |
E76698
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Yemeni Arabic |
C4065
|
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 Yemeni Arabic Context triple: [Yafiʿi Arabic, instanceOf, regional variety of Yemeni Arabic]
-
A.
colloquial Arabic variety
A colloquial Arabic variety is a regionally or socially specific, primarily spoken form of Arabic that differs from Modern Standard Arabic in pronunciation, vocabulary, and grammar.
-
B.
variety of Arabic
chosen
A variety of Arabic is a distinct form of the Arabic language, characterized by its own phonological, lexical, and grammatical features, typically associated with a particular region, community, or social context.
-
C.
Fula language variety
A Fula language variety is a specific regional or social form of the Fula (Fulfulde/Pulaar/Pular) language distinguished by its phonological, lexical, and grammatical features within the broader Fula continuum.
-
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.
Kurdish dialect
A Kurdish dialect is a regional or social variety of the Kurdish language characterized by distinct phonological, lexical, and grammatical features shared by a specific Kurdish-speaking community.
- F. None of above.
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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:23 p.m.