Triple
T14554690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-Persians |
E341507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persianate group |
C34942
|
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: Persianate group Context triple: [Indo-Persians, instanceOf, Persianate group]
-
A.
Persianate dynasty
A Persianate dynasty is a ruling family or political regime that, regardless of its ethnic origin, adopts and promotes Persian language, culture, administrative practices, and aesthetic ideals as the core framework of its governance and elite identity.
-
B.
Sasanian client state
A Sasanian client state was a semi-autonomous polity that retained its own local rulers and internal administration while recognizing the suzerainty of the Sasanian Empire, often providing tribute, military support, and strategic buffer territory.
-
C.
medieval Iranian state
A medieval Iranian state is a historically situated political entity in the Iranian plateau and surrounding regions, characterized by dynastic rule, Persianate administrative and cultural traditions, and interaction with neighboring Islamic and Eurasian powers between roughly the 7th and 15th centuries.
-
D.
Arabian polity
An Arabian polity is a political entity or state structure that governs a defined territory and population within the Arabian Peninsula or broader Arab world, shaped by regional history, culture, and power relations.
-
E.
Aimaq subgroup
Aimaq subgroup refers to a distinct tribal or regional division within the Aimaq people of Afghanistan and neighboring areas, characterized by shared lineage, dialect, and cultural practices.
- F. None of above. chosen
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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:23 a.m.