Triple
T30515635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulaymaniyah dialect |
E776558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Central Kurdish |
C9150
|
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 Central Kurdish Context triple: [Sulaymaniyah dialect, instanceOf, variety of Central Kurdish]
-
A.
Kurdish dialect
chosen
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.
-
B.
variety of the Armenian language
A variety of the Armenian language is a distinct form or dialect of Armenian characterized by unique phonological, lexical, and grammatical features used by a particular community or region.
-
C.
variety of Turkish
A variety of Turkish is a distinct form or dialect of the Turkish language characterized by unique phonological, lexical, and grammatical features associated with a particular region, community, or social group.
-
D.
regional variety of the Kumyk language
A regional variety of the Kumyk language is a geographically defined form of Kumyk that exhibits distinct phonological, lexical, or grammatical features while remaining mutually intelligible with other Kumyk dialects.
-
E.
variety of Central Sama language
A variety of Central Sama language is a specific regional or social form of the Central Sama language distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Central Sama varieties.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:16 p.m.