Triple
T37866129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guido delle Colonne's Historia destructionis Troiae |
E944473
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical romance |
C4255
|
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 romance Context triple: [Guido delle Colonne's Historia destructionis Troiae, instanceOf, historical romance]
-
A.
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.
-
B.
historical novella
A historical novella is a short work of fiction that focuses on a concise, character-driven story set within a carefully researched and vividly depicted past era.
-
C.
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.
-
D.
chivalric romance
chosen
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.
-
E.
Elizabethan romance
Elizabethan romance is a literary genre of the late 16th and early 17th centuries that blends chivalric adventure, idealized love, and elements of fantasy or pastoral life, often in ornate language and complex, episodic plots.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.