Triple

T30721871
Position Surface form Disambiguated ID Type / Status
Subject Regensburg Colloquy (1541) E782174 entity
Predicate instanceOf P0 FINISHED
Object 16th-century historical event 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 historical event
Context triple: [Regensburg Colloquy (1541), instanceOf, 16th-century historical event]
  • A. 15th-century event
    A 15th-century event is a historically significant occurrence that took place between 1401 and 1500, shaped by and contributing to the political, social, cultural, or technological transformations of that period.
  • B. 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.
  • C. 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.
  • D. 14th-century event
    A 14th-century event is a historically significant occurrence between 1301 and 1400 that influenced the social, political, cultural, or economic developments of that period.
  • E. 13th-century event
    A 13th-century event is any significant occurrence, development, or happening that took place between the years 1201 and 1300 CE.
  • 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_69f224acd24481908ed5f96f0d69b5dd completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 8:36 p.m.