Triple
T26413546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David of Burgundy |
E664024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Burgundian prince |
C51533
|
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 prince Context triple: [David of Burgundy, instanceOf, Burgundian prince]
-
A.
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.
-
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.
Capetian prince
A Capetian prince is a male royal born into or descended from the Capetian dynasty, traditionally holding the title and status of a king’s son or close male relative within that ruling house.
-
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.
Bavarian prince
A Bavarian prince is a male member of the royal or formerly ruling house of Bavaria, traditionally holding hereditary titles, privileges, and social status within the region’s historical 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:39 p.m.