Triple
T10927819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Burgundy (as overlord of the Burgundian Netherlands) |
E258116
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late medieval prince |
C5254
|
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: late medieval prince Context triple: [Duke of Burgundy (as overlord of the Burgundian Netherlands), instanceOf, late medieval prince]
-
A.
late medieval ruler
chosen
A late medieval ruler is a sovereign who governed a kingdom or principality in Europe roughly between the 13th and 15th centuries, navigating feudal structures, emerging centralized authority, and complex dynastic, religious, and military conflicts.
-
B.
medieval king
A medieval king is a sovereign ruler who holds supreme political, military, and often religious authority over a kingdom, typically justified by hereditary right and divine sanction.
-
C.
English prince
An English prince is a male member of the British royal family, typically a son or close male-line descendant of the monarch, who holds the title of "Prince" and may perform ceremonial, diplomatic, and public duties on behalf of the Crown.
-
D.
Christian prince
A Christian prince is a sovereign or ruling noble whose authority and governance are explicitly shaped by Christian beliefs, values, and ecclesiastical relationships.
-
E.
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.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:22 p.m.