Triple
T22530887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero and Leander |
E557032
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance poem |
C40772
|
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: Renaissance poem Context triple: [Hero and Leander, instanceOf, Renaissance poem]
-
A.
Elizabethan poem
An Elizabethan poem is a lyrical or narrative verse composed during or in the style of England’s Elizabethan era, typically characterized by structured meter, rich imagery, and themes of love, politics, or humanism.
-
B.
literary renaissance
A literary renaissance is a period of renewed creativity, innovation, and flourishing in literature, often marked by a revival of classical influences and the emergence of new styles, themes, and voices.
-
C.
Renaissance play
A Renaissance play is a dramatic work written during the European Renaissance that blends classical influences with contemporary themes, often exploring humanism, politics, and complex character psychology through verse and staged performance.
-
D.
Renaissance literature work
chosen
A Renaissance literature work is a written piece, typically from the 14th to 17th centuries, that reflects the era’s revival of classical learning, humanist ideals, and experimentation with new literary forms and vernacular languages.
-
E.
Renaissance mass
A Renaissance mass is a large-scale, multi-movement sacred musical setting of the Catholic liturgy, typically for voices, characterized by imitative polyphony and based on techniques such as cantus firmus, parody, or paraphrase.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:51 p.m.