Triple
T5941180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Iranian languages |
E132168
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the 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: branch of the Iranian languages Context triple: [Old Iranian languages, instanceOf, branch of the 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.
branch of Semitic languages
A branch of Semitic languages is a subgroup within the Semitic language family comprising closely related languages that share common historical origins, structural features, and vocabulary.
-
D.
branch of the Turkic languages
A branch of the Turkic languages is a subgroup of related Turkic languages that share a common historical origin, structural features, and vocabulary within the broader Turkic language family.
-
E.
branch of the Germanic languages
A branch of the Germanic languages is a subgroup of related Germanic languages that share a common historical origin, structural features, and vocabulary, such as the North, West, or (extinct) East Germanic branches.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:01 p.m.