Triple
T14410516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gundobad |
E357310
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Burgundian king |
C33948
|
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: Burgundian king Context triple: [Gundobad, instanceOf, Burgundian king]
-
A.
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.
-
B.
Duke of Burgundy
The Duke of Burgundy is a high-ranking noble title historically associated with the powerful rulers of the Burgundy region, often serving as influential political and military leaders in medieval and early modern Europe.
-
C.
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.
-
D.
Duke of Lorraine
The Duke of Lorraine is a noble title historically held by the sovereign ruler of the Duchy of Lorraine, a strategically important region in northeastern France that played a key role in European dynastic and territorial politics.
-
E.
King of France
The King of France is the sovereign monarch who historically ruled the Kingdom of France, embodying supreme political authority, symbolic national leadership, and dynastic continuity until the abolition of the monarchy.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:17 a.m.