Triple
T9178386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diet of Augsburg (1530) |
E220258
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | assembly of the Holy Roman Empire |
C25772
|
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: assembly of the Holy Roman Empire Context triple: [Diet of Augsburg (1530), instanceOf, assembly of the Holy Roman Empire]
-
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.
imperial confederation
An imperial confederation is a loose union of semi-autonomous states or territories under the overarching authority of an empire, which coordinates common policies while allowing substantial local self-rule.
-
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. 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:23 p.m.