Triple
T1472851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurdish language |
E27174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Iranian language |
C5771
|
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: Western Iranian language Context triple: [Kurdish language, instanceOf, Western Iranian language]
-
A.
Northwest Iranian language
chosen
A Northwest Iranian language is a member of the western branch of the Iranian languages spoken primarily in regions of northwestern Iran and neighboring areas, characterized by shared phonological, lexical, and grammatical features distinct from Southwest Iranian languages.
-
B.
Eastern Romance language
An Eastern Romance language is a member of the Romance branch of the Indo-European language family that evolved from Eastern varieties of Vulgar Latin, primarily spoken in the Balkans and surrounding regions.
-
C.
Semitic language
A Semitic language is a member of a family of related languages originating in the Middle East and North Africa, characterized by root-based morphology and including languages such as Arabic, Hebrew, and Amharic.
-
D.
Northwest Caucasian language
A Northwest Caucasian language is a member of a small family of indigenous languages spoken in the northwestern Caucasus region, characterized by complex consonant systems, minimal vowel inventories, and rich verbal morphology.
-
E.
Turkic language
A Turkic language is a member of a family of closely related languages spoken across a vast area from Eastern Europe and Anatolia through Central Asia to Siberia and Western China, characterized by agglutinative morphology, vowel harmony, and similar grammatical structures.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
Created at: March 1, 2026, 8:01 p.m.