Triple
T21570709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robin Hood plays |
E532272
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval-themed plays |
C44988
|
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: medieval-themed plays Context triple: [Robin Hood plays, instanceOf, medieval-themed plays]
-
A.
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.
-
B.
medieval film
A medieval film is a motion picture set in or thematically centered on the Middle Ages, typically featuring historical or pseudo-historical settings, feudal societies, knights, castles, and related cultural or mythological elements.
-
C.
medieval court
A medieval court is the political and social center surrounding a monarch or noble, where governance, justice, ceremony, and daily life of the ruling elite are conducted.
-
D.
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.
-
E.
medieval charm
A medieval charm is a small, often inscribed object or spoken formula believed to harness supernatural or divine power for protection, healing, or influencing events in accordance with medieval beliefs and practices.
- F. None of above. chosen
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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:30 p.m.