Triple
T22208481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godfrey I, Count of Louvain |
E548877
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Lower Lotharingia |
C27058
|
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: Duke of Lower Lotharingia Context triple: [Godfrey I, Count of Louvain, instanceOf, Duke of Lower Lotharingia]
-
A.
Duke of Lotharingia
chosen
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.
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.
-
C.
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.
-
D.
Duke of Swabia
The Duke of Swabia was a high-ranking medieval noble who ruled the historical region of Swabia within the Holy Roman Empire, holding significant military, political, and territorial authority.
-
E.
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.
- 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:36 p.m.