Triple
T4809966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gijsbrecht van Aemstel |
E107043
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 17th-century play |
C16412
|
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: 17th-century play Context triple: [Gijsbrecht van Aemstel, instanceOf, 17th-century play]
-
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.
17th-century book
A 17th-century book is a bound collection of printed or handwritten pages produced between 1601 and 1700, reflecting the period’s materials, typography, and intellectual, religious, or political culture.
-
C.
Caroline-era play
A Caroline-era play is a dramatic work written and performed in England during the reign of King Charles I (1625–1649), characterized by elaborate courtly themes, stylistic refinement, and often a blend of tragic and romantic elements.
-
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.
17th-century person
A 17th-century person is an individual who lived during the 1600s, shaped by the political, religious, scientific, and cultural transformations of the early modern period.
- 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_69bd43f779448190b92885cb70abb6c2 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:23 p.m.