Triple
T8326279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Dream of John Ball |
E194961
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical fantasy work |
C24253
|
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: historical fantasy work Context triple: [A Dream of John Ball, instanceOf, historical fantasy work]
-
A.
historical adventure fiction
Historical adventure fiction is a genre that blends meticulously researched past settings and events with fast-paced, often perilous journeys or quests, emphasizing action, exploration, and personal heroism within a specific historical context.
-
B.
medieval literary work
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.
-
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.
didactic historical romance
A didactic historical romance is a love story set in a carefully rendered past era that explicitly aims to teach readers moral, social, or historical lessons through its characters’ romantic journeys.
-
E.
dark fantasy work
A dark fantasy work is a story set in a fantastical world that blends supernatural or magical elements with grim, eerie, or morally ambiguous themes, often emphasizing horror, tragedy, and psychological tension.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:56 p.m.