Triple

T21233704
Position Surface form Disambiguated ID Type / Status
Subject Musurgia Universalis E523287 entity
Predicate instanceOf P0 FINISHED
Object seventeenth-century book C1302 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: seventeenth-century book
Context triple: [Musurgia Universalis, instanceOf, seventeenth-century book]
  • A. 17th-century book chosen
    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.
  • B. eighteenth-century publication
    An eighteenth-century publication is a printed work—such as a book, pamphlet, periodical, or broadside—produced and distributed between 1700 and 1799, reflecting the printing technologies, literary forms, and cultural contexts of that era.
  • C. 8th-century book
    An 8th-century book is a handwritten manuscript, often on parchment or vellum, created during the 700s CE and typically featuring religious, legal, or scholarly texts preserved in early medieval script and binding styles.
  • D. Renaissance treatise
    A Renaissance treatise is a systematic, often humanist-influenced written work from roughly the 14th to 17th centuries that explores a specific subject—such as art, science, politics, or philosophy—through structured argument and scholarly discourse.
  • E. 17th-century play
    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.
  • 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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
Created at: April 16, 2026, 3:45 p.m.