Triple
T20012395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmont |
E494620
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Shakespearean setting |
C6044
|
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 setting Context triple: [Belmont, instanceOf, Shakespearean setting]
-
A.
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.
-
B.
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.
-
C.
English Renaissance drama
chosen
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.
-
D.
Arthurian setting
An Arthurian setting is a mythic medieval world inspired by the legends of King Arthur, featuring chivalric knights, enchanted forests, mystical artifacts, and the tension between noble ideals and human frailty.
-
E.
literary setting
A literary setting is the time, place, and social environment in which a story’s events occur, shaping mood, character behavior, and plot development.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:34 p.m.