Triple
T35967325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sīrat ʿAntar |
E1040180
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Arabic epic romance |
C12780
|
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: medieval Arabic epic romance Context triple: [Sīrat ʿAntar, instanceOf, medieval Arabic epic romance]
-
A.
chivalric romance
A chivalric romance is a medieval narrative genre that recounts the adventures of knights engaged in quests that blend courtly love, martial valor, and the supernatural within an idealized feudal world.
-
B.
Byzantine romance
Byzantine romance is a medieval Greek narrative genre, typically in prose or verse, that weaves together chivalric adventure, idealized love, and religious or moral themes within a Byzantine cultural and historical setting.
-
C.
Arthurian romance
Arthurian romance is a medieval narrative tradition centered on King Arthur and his court, blending chivalric adventure, courtly love, and the supernatural to explore ideals of knighthood, honor, and destiny.
-
D.
character in a chivalric romance
A character in a chivalric romance is an often idealized figure—such as a knight, noble lady, or sorcerer—whose adventures, virtues, and trials embody the codes of honor, courtly love, and heroic quest central to the narrative.
-
E.
medieval literary work
chosen
A medieval literary work is a written or orally transmitted text from roughly the 5th to the 15th century that reflects the cultural, religious, and social contexts of the Middle Ages through genres such as epics, romances, hagiographies, chronicles, and lyric poetry.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.