Triple

T23691943
Position Surface form Disambiguated ID Type / Status
Subject Crypto-Calvinist controversy E585324 entity
Predicate instanceOf P0 FINISHED
Object 16th-century religious controversy C26999 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: 16th-century religious controversy
Context triple: [Crypto-Calvinist controversy, instanceOf, 16th-century religious controversy]
  • A. 16th-century religious event chosen
    A 16th-century religious event is a historically situated occurrence, such as a council, reform, conflict, or ritual, that reflects and influences the era’s intense transformations in faith, doctrine, and church authority.
  • B. 16th-century conflict
    A 16th-century conflict is a historically documented military, political, or religious struggle that occurred between 1501 and 1600, involving organized groups or states and significantly influencing the social and geopolitical landscape of the early modern period.
  • C. 16th-century theological document
    A 16th-century theological document is a written work from the 1500s that articulates, debates, or codifies religious doctrines, beliefs, or practices within the historical context of Reformation-era Christianity.
  • D. Puritan controversy
    A Puritan controversy is a historical or theological dispute arising within Puritan communities over matters of doctrine, church governance, or moral practice that challenged established religious authority and norms.
  • E. 16th-century council
    A 16th-century council is a formal assembly of political, religious, or civic authorities convened during the 1500s to deliberate and decide on matters of governance, doctrine, law, or public policy.
  • 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_69e249037ce0819088b149608e98f685 completed April 17, 2026, 2:51 p.m.
Created at: April 17, 2026, 6:52 p.m.