Triple
T1918564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwestern Iranian languages |
E40074
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subgroup of Iranian languages |
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: subgroup of Iranian languages Context triple: [Northwestern Iranian languages, instanceOf, subgroup of Iranian languages]
-
A.
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.
-
B.
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.
-
C.
language family subgroup
A language family subgroup is a set of closely related languages within a larger language family that share a more recent common ancestor and distinctive linguistic features.
-
D.
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.
-
E.
Dravidian language
A Dravidian language is a member of a family of primarily South Indian and Sri Lankan languages, such as Tamil, Telugu, Kannada, and Malayalam, that share common historical origins and structural features distinct from Indo-European languages.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:35 p.m.