Triple
T5805806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kay Khosrow |
E128741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iranian epic hero |
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: Iranian epic hero Context triple: [Kay Khosrow, instanceOf, Iranian epic hero]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
character in the Iliad
A character in the Iliad is an individual—mortal or divine—who participates in, influences, or is affected by the events of the Trojan War as narrated in Homer’s epic.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:52 p.m.