Triple
T36410859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shakespearean histories |
E896875
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical plays |
C11386
|
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 plays Context triple: [Shakespearean histories, instanceOf, historical plays]
-
A.
historical drama
chosen
A historical drama is a narrative work that portrays fictionalized or real characters and events set in a past era, emphasizing period-accurate settings, costumes, and social conditions to explore human experiences within their historical context.
-
B.
historical opera
A historical opera is a staged musical drama that portrays significant past events or figures through a combination of vocal performance, orchestral music, and theatrical storytelling.
-
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.
historic theater
A historic theater is a long-standing performance venue of architectural or cultural significance that has hosted artistic events across generations and often reflects the social and artistic heritage of its era.
-
E.
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.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.