Triple

T8810444
Position Surface form Disambiguated ID Type / Status
Subject Imperial coronation journeys E209646 entity
Predicate instanceOf P0 FINISHED
Object Holy Roman Empire tradition C25102 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: Holy Roman Empire tradition
Context triple: [Imperial coronation journeys, instanceOf, Holy Roman Empire tradition]
  • A. imperial state of the Holy Roman Empire
    An imperial state of the Holy Roman Empire was a semi-autonomous political entity—such as a duchy, principality, city, or ecclesiastical territory—directly subject to the authority of the emperor and the imperial diet rather than to any intermediate lord.
  • B. office of the Holy Roman Empire
    The office of the Holy Roman Empire is a formal position within the imperial hierarchy responsible for specific administrative, judicial, ceremonial, or territorial duties under the authority of the Holy Roman Emperor.
  • C. 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.
  • D. 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.
  • E. Habsburg
    Habsburg: A powerful European royal dynasty that ruled vast territories including the Holy Roman Empire, Spain, and Austria for centuries through strategic marriages and political alliances.
  • F. None of above. chosen

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_69ca8363f3308190a47e3f1ebd51f613 completed March 30, 2026, 2:06 p.m.
Created at: March 30, 2026, 6:45 p.m.