Triple

T10869492
Position Surface form Disambiguated ID Type / Status
Subject First Zurich Disputation E256613 entity
Predicate instanceOf P0 FINISHED
Object Reformation event C1474 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: Reformation event
Context triple: [First Zurich Disputation, instanceOf, Reformation event]
  • A. Christian reform movement
    A Christian reform movement is a religious initiative within Christianity aimed at renewing faith, correcting perceived doctrinal or moral errors, and transforming church practices or social structures in light of biblical principles.
  • B. 16th-century religious event
    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.
  • C. Protestant reform measure
    A Protestant reform measure is a specific policy, decree, or action implemented to align religious, political, or social practices with Protestant theological principles and church governance.
  • D. event in church history chosen
    An event in church history is a significant occurrence or development within the life of the Christian church that influences its doctrine, practice, structure, or relationship with society over time.
  • E. Tudor-era reform
    Tudor-era reform refers to the series of political, religious, and administrative changes in 16th-century England, particularly under Henry VIII and Elizabeth I, that redefined the monarchy’s power, broke from the Roman Catholic Church, and laid foundations for the modern English state.
  • 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_69d6aa83d1448190a66d93c32394d21f completed April 8, 2026, 7:20 p.m.
Created at: April 8, 2026, 9:20 p.m.