Triple
T11877714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudolf I of Germany |
E282573
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | king of Germany |
C5253
|
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: king of Germany Context triple: [Rudolf I of Germany, instanceOf, king of Germany]
-
A.
King of Germany
chosen
The King of Germany is a conceptual class representing a sovereign monarch who historically ruled over the German kingdom within the Holy Roman Empire, embodying supreme political and symbolic authority over its territories and subjects.
-
B.
German Emperor
A German Emperor is the sovereign ruler who held the imperial title over the German Empire, symbolizing supreme political and military authority within the unified German state from 1871 to 1918.
-
C.
anti-king of Germany
An anti-king of Germany was a rival claimant elected by a faction of princes in opposition to a reigning or officially recognized German king or Holy Roman Emperor, typically during periods of dynastic or political conflict.
-
D.
prince of the Holy Roman Empire
A prince of the Holy Roman Empire was a secular or ecclesiastical ruler who held immediate authority under the emperor, possessing territorial sovereignty and a vote in the Imperial Diet.
-
E.
King of Lotharingia
The King of Lotharingia is the sovereign ruler of the medieval kingdom of Lotharingia, governing its territories, administering justice, leading its armies, and representing its authority within the broader context of the Frankish and later Holy Roman Empire realms.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.