Triple
T18522382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudolph II of Upper Burgundy |
E452619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | King of Upper Burgundy |
C40546
|
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 Upper Burgundy Context triple: [Rudolph II of Upper Burgundy, instanceOf, King of Upper Burgundy]
-
A.
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.
-
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.
Duke of Lotharingia
The Duke of Lotharingia is a high-ranking noble who governs the historical region of Lotharingia, wielding military, judicial, and administrative authority on behalf of the sovereign.
-
D.
King of the Franks
The King of the Franks was the sovereign ruler of the Frankish people and their territories, wielding military, political, and legal authority over the Frankish kingdom in early medieval Europe.
-
E.
Ostrogothic king
An Ostrogothic king is the sovereign ruler of the Ostrogoths, a Germanic people who established and governed kingdoms—most notably in Italy—during the late antique and early medieval periods.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:37 a.m.