Triple
T24258272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichsfürstenstand |
E604632
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Stand des Heiligen Römischen Reiches |
C48949
|
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: Stand des Heiligen Römischen Reiches Context triple: [Reichsfürstenstand, instanceOf, Stand des Heiligen Römischen Reiches]
-
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.
imperial circle of the Holy Roman Empire
An imperial circle of the Holy Roman Empire was a regional administrative and defensive grouping of territories created to organize imperial governance, taxation, and military obligations within a defined area of the Empire.
-
D.
Handelsbündnis
Ein Handelsbündnis ist ein Zusammenschluss von Staaten oder Organisationen, der durch Abkommen den gegenseitigen Handel erleichtert, fördert und reguliert.
-
E.
King of Westphalia
The King of Westphalia was the sovereign ruler of the short-lived Kingdom of Westphalia (1807–1813), a Napoleonic client state in central Europe governed primarily by Napoleon’s brother Jérôme Bonaparte.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:06 a.m.