Triple

T5911765
Position Surface form Disambiguated ID Type / Status
Subject Reservatum ecclesiasticum E131476 entity
Predicate instanceOf P0 FINISHED
Object provision of the Peace of Augsburg C3551 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: provision of the Peace of Augsburg
Context triple: [Reservatum ecclesiasticum, instanceOf, provision of the Peace of Augsburg]
  • A. engagement of the Thirty Years' War
    An engagement of the Thirty Years' War is a specific military confrontation—ranging from small skirmishes to major battles—fought between participating states or factions within the broader conflict that ravaged Central Europe from 1618 to 1648.
  • B. conflict in the Holy Roman Empire
    Conflict in the Holy Roman Empire encompasses the political, religious, and territorial struggles among emperors, princes, cities, and external powers that shaped the empire’s fragmented structure and shifting balance of authority.
  • C. institution of the Catholic Monarchy
    The institution of the Catholic Monarchy is a form of early modern governance in which a monarch legitimized by Catholic doctrine wields centralized political, religious, and cultural authority over a composite realm.
  • D. agreement between state and church chosen
    An agreement between state and church is a formal arrangement that defines the rights, responsibilities, and mutual relations between governmental authorities and religious institutions.
  • E. administrative district of the Holy Roman Empire
    An administrative district of the Holy Roman Empire was a territorial unit governed by imperial or local authorities to organize political, judicial, and fiscal control within the Empire’s decentralized structure.
  • 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_69c008593a44819081a07ae0efe6c574 completed March 22, 2026, 3:18 p.m.
Created at: March 22, 2026, 3:59 p.m.