Triple
T9186615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kermanic languages |
E220474
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 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: Iranian languages subgroup Context triple: [Kermanic languages, instanceOf, Iranian languages subgroup]
-
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.
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.
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.
-
E.
Elamite language
Elamite language is an extinct language isolate once spoken in the ancient kingdom of Elam in what is now southwestern Iran, known primarily from cuneiform inscriptions dating from the 3rd to 1st millennia BCE.
- 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.