Triple
T31399474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuristani branch of Indo-Iranian |
E800955
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subgroup of Indo-Iranian languages |
C7357
|
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 Indo-Iranian languages Context triple: [Nuristani branch of Indo-Iranian, instanceOf, subgroup of Indo-Iranian languages]
-
A.
Aslian language subgroup
The Aslian language subgroup comprises a cluster of closely related Austroasiatic languages spoken primarily by indigenous Orang Asli communities in Peninsular Malaysia and southern Thailand.
-
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.
Indo-European language branch
chosen
The Indo-European language branch is a major subgroup within the Indo-European language family comprising closely related languages that share a common ancestral origin and distinctive linguistic features.
-
D.
Indo-European language
An Indo-European language is a member of a large family of related languages spoken across Europe and parts of Asia, all descended from a common prehistoric ancestor known as Proto-Indo-European.
-
E.
Tibeto-Burman languages subgroup
The Tibeto-Burman languages subgroup is a major branch of the Sino-Tibetan language family comprising hundreds of related languages spoken primarily in the Himalayas, Southeast Asia, and parts of East Asia.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:19 p.m.