Triple

T25668816
Position Surface form Disambiguated ID Type / Status
Subject The Book of the Courtier E643602 entity
Predicate instanceOf P0 FINISHED
Object Renaissance dialogue C1211 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: Renaissance dialogue
Context triple: [The Book of the Courtier, instanceOf, Renaissance dialogue]
  • 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. Renaissance mass
    A Renaissance mass is a large-scale, multi-movement sacred musical setting of the Catholic liturgy, typically for voices, characterized by imitative polyphony and based on techniques such as cantus firmus, parody, or paraphrase.
  • C. Renaissance humanism
    Renaissance humanism was an intellectual and cultural movement of the 14th–16th centuries that revived classical Greco-Roman learning and emphasized human potential, individual dignity, and secular scholarship alongside traditional religious beliefs.
  • 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. Platonic dialogue chosen
    A Platonic dialogue is a philosophical text, typically featuring Socrates, in which ideas are explored through question-and-answer conversations that probe definitions, assumptions, and the nature of knowledge and virtue.
  • 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_69e77e7e45648190a068ed3faa8016ea completed April 21, 2026, 1:41 p.m.
Created at: April 21, 2026, 7:10 p.m.