Triple
T29607904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Tetralogy |
E754627
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Shakespearean history cycle |
C15180
|
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: Shakespearean history cycle Context triple: [First Tetralogy, instanceOf, Shakespearean history cycle]
-
A.
English Renaissance drama
English Renaissance drama is a body of theatrical works produced in England roughly between the late 15th and early 17th centuries, characterized by poetic language, complex characters, and a blend of classical influences with contemporary social, political, and religious themes.
-
B.
Renaissance play
chosen
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.
-
C.
historical novel cycle
A historical novel cycle is a series of interrelated historical fiction works that share a common setting, characters, or overarching narrative across multiple volumes.
-
D.
tapestry cycle
A tapestry cycle is a series of related woven hangings designed and produced as a coordinated group to depict a continuous narrative, theme, or set of events.
-
E.
Elizabethan-style theatre
An Elizabethan-style theatre is a circular or polygonal, open-air playhouse with tiered galleries and a thrust stage projecting into a central yard, designed to host live performances for diverse audiences in the late 16th and early 17th centuries.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:26 p.m.