Triple
T18130871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Shah Zaman |
E434005
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in One Thousand and One Nights |
C39688
|
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: character in One Thousand and One Nights Context triple: [King Shah Zaman, instanceOf, character in One Thousand and One Nights]
-
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 Silappatikaram
A character in Silappatikaram is an individual—mortal, divine, or symbolic—whose actions, relationships, and moral choices drive the epic’s exploration of justice, fate, and dharma in ancient Tamil society.
-
C.
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.
-
D.
character in The Canterbury Tales
A character in The Canterbury Tales is an individual pilgrim, each with distinct social background, personality, and motivations, who narrates a tale that reflects and critiques the values and tensions of late medieval English society.
-
E.
Character in the Ramayana
A Character in the Ramayana is an individual—divine, human, or demonic—whose actions, relationships, and moral choices drive the epic’s narrative and embody its spiritual and ethical teachings.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:29 a.m.