Triple
T5942836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esfandiyar |
E132208
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iranian mythological figure |
C3096
|
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 mythological figure Context triple: [Esfandiyar, instanceOf, Iranian mythological figure]
-
A.
Mesopotamian legendary figure
A Mesopotamian legendary figure is a mythic or semi-divine personage from ancient Mesopotamian cultures whose stories, deeds, and attributes embody religious beliefs, moral values, and cosmological ideas preserved in epics, hymns, and ritual texts.
-
B.
mythological figure
chosen
A mythological figure is a legendary being or character from traditional stories and belief systems, often embodying cultural values, natural forces, or supernatural powers.
-
C.
Indo-Iranian deity
An Indo-Iranian deity is a divine figure originating from the shared religious and mythological traditions of the ancient Indo-Aryan and Iranian peoples, often associated with natural forces, social order, and cosmic principles.
-
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.
figure in Greek mythology
A figure in Greek mythology is a character—divine, heroic, or monstrous—who appears in the traditional myths of ancient Greece and embodies cultural values, natural forces, or moral lessons.
- 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_69c00869d3308190af89b2453e0f7546 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:01 p.m.