Triple
T2091366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry III of France |
E32677
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Anjou |
C9798
|
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 Anjou Context triple: [Henry III of France, instanceOf, Duke of Anjou]
-
A.
Duke of Orléans
The Duke of Orléans is a French noble title traditionally held by a close male relative of the reigning king, often associated with significant political influence, territorial holdings around Orléans, and a prominent role in royal succession and court affairs.
-
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.
Duke of Savoy
The Duke of Savoy was the hereditary ruler of the historical Duchy of Savoy, a significant European principality that played a key role in the politics of Italy and France from the late Middle Ages until its elevation to a kingdom.
-
D.
Dauphine of France
The Dauphine of France is the title given to the wife of the Dauphin, the heir apparent to the French throne, signifying her status as the future queen consort.
-
E.
Duke of Normandy
The Duke of Normandy was a medieval noble title denoting the sovereign or semi-sovereign ruler of the Duchy of Normandy, a powerful feudal territory in northwestern France that played a pivotal role in European politics, especially after its dukes became kings of England.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:43 p.m.