Triple
T13163714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electorate of Regensburg |
E312791
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial electorate |
C1441
|
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: imperial electorate Context triple: [Electorate of Regensburg, instanceOf, imperial electorate]
-
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.
prince-electorate
chosen
A prince-electorate is a sovereign or semi-sovereign ruler within the Holy Roman Empire who held the hereditary right to participate in the election of the emperor.
-
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.
assembly of the Holy Roman Empire
The assembly of the Holy Roman Empire was a representative gathering of the Empire’s princes, ecclesiastical leaders, and imperial cities convened to deliberate and decide on matters of law, policy, and governance under the authority of the emperor.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:13 p.m.