Triple
T2047888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto I, Holy Roman Emperor |
E45495
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 10th-century German ruler |
C5149
|
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: 10th-century German ruler Context triple: [Otto I, Holy Roman Emperor, instanceOf, 10th-century German ruler]
-
A.
King of Germany
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.
King of the Romans
chosen
The King of the Romans was the title used by the elected ruler of the Holy Roman Empire, designating him as emperor-designate pending papal coronation as Holy Roman Emperor.
-
C.
Anglo-Saxon ruler
An Anglo-Saxon ruler is a monarch or chieftain who governed territories in early medieval England, exercising military, legal, and religious authority over their people.
-
D.
Anglo-Saxon monarch
An Anglo-Saxon monarch is a hereditary or elected ruler who governed one of the early medieval English kingdoms prior to the Norman Conquest, wielding military, legal, and religious authority over their realm.
-
E.
King in Prussia
King in Prussia was the royal title used by the Hohenzollern rulers of Brandenburg-Prussia from 1701 to 1772, signifying their kingship over Prussia while remaining nominally subordinate to the Holy Roman Emperor within the empire.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:39 p.m.