Triple
T17000044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinrich I of Germany |
E412418
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German king |
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: German king Context triple: [Heinrich I of Germany, instanceOf, German king]
-
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.
Burgundian king
A Burgundian king is the sovereign ruler of the historical Kingdom or later Duchy of Burgundy, exercising political, military, and judicial authority over its territories and people.
-
C.
Bavarian monarch
A Bavarian monarch is the sovereign ruler of Bavaria, historically holding supreme political authority and symbolic leadership over the Bavarian state and its people.
-
D.
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.
-
E.
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.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:32 a.m.