Triple

T18542632
Position Surface form Disambiguated ID Type / Status
Subject The Forced Marriage E453137 entity
Predicate instanceOf P0 FINISHED
Object Restoration 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: Restoration play
Context triple: [The Forced Marriage, instanceOf, Restoration 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 play chosen
    A 17th-century play is a dramatic work written and typically performed between 1601 and 1700, reflecting the period’s distinctive theatrical conventions, language, and social, political, or religious concerns.
  • C. Baroque theatre
    Baroque theatre is a style of theatrical architecture and performance from the 17th and early 18th centuries characterized by elaborate stage machinery, ornate decoration, dramatic lighting, and highly stylized acting and spectacle.
  • 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. 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_69d8d388b0c881908e610a1c45b52640 completed April 10, 2026, 10:40 a.m.
Created at: April 10, 2026, 11:38 a.m.