Triple
T31607905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iranian linguistics |
E806542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subfield of Indo-Iranian linguistics |
C4688
|
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: subfield of Indo-Iranian linguistics Context triple: [Iranian linguistics, instanceOf, subfield of Indo-Iranian linguistics]
-
A.
subfield of linguistics
chosen
A subfield of linguistics is a specialized branch of the study of language that focuses on a particular aspect of linguistic structure, use, or development, such as phonetics, syntax, semantics, or sociolinguistics.
-
B.
branch of Iranian languages
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.
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.
-
D.
branch of languages
A branch of languages is a subgroup within a language family consisting of closely related languages that evolved from a more recent common ancestor.
-
E.
Dardic language
A Dardic language is a member of a subgroup of the Indo-Aryan languages spoken primarily in the mountainous regions of northern Pakistan, northwestern India, and eastern Afghanistan, characterized by distinct phonological and lexical features.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:35 p.m.