Triple
T20931015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | killing of Esfandiyar |
E515469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | episode in Shahnameh |
C41876
|
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: episode in Shahnameh Context triple: [killing of Esfandiyar, instanceOf, episode in Shahnameh]
-
A.
character in Shahnameh
A character in Shahnameh is a mytho-historical figure—heroic, royal, or demonic—whose actions, lineage, and moral choices drive the epic’s intertwined tales of Iran’s legendary past.
-
B.
character in the Shahnameh
A character in the Shahnameh is a mytho-historical figure—heroic, royal, or supernatural—whose life and deeds embody the epic’s themes of honor, fate, and the rise and fall of Iranian dynasties.
-
C.
episode of an epic poem
chosen
An episode of an epic poem is a self-contained narrative unit within the larger epic that advances the overarching plot, develops characters, or illustrates key themes through a specific event or sequence of actions.
-
D.
episode in the Epic of Gilgamesh
An episode in the Epic of Gilgamesh is a distinct narrative unit within the larger poem that presents a specific adventure, challenge, or transformation in Gilgamesh’s journey, contributing to the overarching themes of mortality, friendship, and the search for meaning.
-
E.
Iranian epic hero
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.
- 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.