Triple
T30463450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kayanian cycle |
E775071
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iranian legendary tradition |
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 tradition Context triple: [Kayanian cycle, instanceOf, Iranian legendary tradition]
-
A.
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.
-
B.
Iranian legendary dynasty
chosen
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.
-
C.
European legend
A European legend is a traditional narrative rooted in the history, folklore, and cultural imagination of European peoples, often blending real events or places with mythical, supernatural, or moral elements.
-
D.
Balochi folklore tale
A Balochi folklore tale is a traditional narrative from the Baloch people that weaves together local history, moral lessons, and cultural values through stories of heroes, spirits, and everyday life.
-
E.
era in Iranian history
An era in Iranian history is a distinct period characterized by specific political structures, cultural developments, social dynamics, and major events that collectively define a recognizable phase in the historical evolution of Iran.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:10 p.m.