Triple
T9186614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kermanic languages |
E220474
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northwestern Iranian languages subgroup |
C7624
|
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: Northwestern Iranian languages subgroup Context triple: [Kermanic languages, instanceOf, Northwestern Iranian languages subgroup]
-
A.
Northwest Iranian language
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.
branch of Iranian languages
chosen
A branch of Iranian languages is a subgroup within the Iranian language family comprising closely related languages that share a common historical origin, structural features, and geographic distribution.
-
C.
Munda languages subgroup
The Munda languages subgroup is a branch of the Austroasiatic language family spoken primarily in eastern and central India, characterized by agglutinative morphology and distinctive phonological and syntactic features.
-
D.
Aimaq subgroup
Aimaq subgroup refers to a distinct tribal or regional division within the Aimaq people of Afghanistan and neighboring areas, characterized by shared lineage, dialect, and cultural practices.
-
E.
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.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:24 p.m.