Triple
T1940328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iranian peoples |
E41537
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indo-Iranian peoples |
C5749
|
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: Indo-Iranian peoples Context triple: [Iranian peoples, instanceOf, Indo-Iranian peoples]
-
A.
Indo-Aryan people
chosen
Indo-Aryan people are a diverse group of ethnolinguistic communities in South Asia who speak Indo-Aryan languages, a major branch of the Indo-European language family, and share related historical and cultural roots.
-
B.
Samoyedic people
Samoyedic people are a group of indigenous peoples of northern Eurasia, primarily in northern Russia, who speak Samoyedic languages of the Uralic family and traditionally practice reindeer herding, fishing, and hunting in Arctic and subarctic environments.
-
C.
Finno-Ugric people
Finno-Ugric people are a group of ethnolinguistic populations in Northern and Eastern Europe and Western Siberia who speak Finno-Ugric languages, including Finns, Estonians, and various Uralic-speaking minorities such as the Sami, Mari, and Udmurts.
-
D.
Northwest Caucasian people
Northwest Caucasian people are an indigenous group of ethnic communities native to the northwestern Caucasus region, characterized by distinct languages, cultures, and historical traditions.
-
E.
Parsi
Parsi is a conceptual class representing a member of the Zoroastrian community in the Indian subcontinent, characterized by shared religious beliefs, cultural practices, and historical lineage tracing back to Persian Zoroastrians who migrated to India.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:36 p.m.