Triple
T5385905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pishdadian dynasty |
E120200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iranian legendary dynasty |
C18418
|
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: Iranian legendary dynasty Context triple: [Pishdadian dynasty, instanceOf, Iranian legendary dynasty]
-
A.
Achaemenid ruler
An Achaemenid ruler is a monarch of the ancient Persian Achaemenid Empire who exercised centralized authority over a vast, multicultural territory through a system of satrapies, royal roads, and imperial administration.
-
B.
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.
-
C.
Achaemenid noble
An Achaemenid noble is a high-ranking member of the Persian aristocracy who held land, military command, and administrative authority under the Achaemenid Empire, often serving as a close supporter and regional representative of the Great King.
-
D.
member of the Pahlavi dynasty
A member of the Pahlavi dynasty is an individual belonging by blood or marriage to the Iranian royal family that ruled Iran from 1925 until the 1979 Islamic Revolution.
-
E.
Byzantine imperial dynasty
A Byzantine imperial dynasty is a succession of related rulers who governed the Eastern Roman (Byzantine) Empire, shaping its political, religious, and cultural life over multiple generations.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
Created at: March 20, 2026, 2:03 p.m.