Triple
T20931790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nowzar |
E515488
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persian legendary ruler |
C18904
|
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: Persian legendary ruler Context triple: [Nowzar, instanceOf, Persian legendary ruler]
-
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.
Sasanian king
A Sasanian king is the sovereign ruler of the Sasanian Empire, wielding supreme political, military, and religious authority over its territories and subjects.
-
C.
Iranian epic hero
chosen
An Iranian epic hero is a larger-than-life figure in Persian mythology and literature who embodies ideals of bravery, honor, and loyalty while undertaking extraordinary quests that shape the fate of their people.
-
D.
Iranian legendary dynasty
An Iranian legendary dynasty is a mytho-historical royal lineage in Iranian tradition, often featured in epic literature like the Shahnameh, that symbolizes ideal kingship, cultural values, and the cosmic struggle between good and evil.
-
E.
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.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:49 p.m.