Triple
T7773575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis Jean Marie de Bourbon, Duke of Penthièvre |
E179132
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Penthièvre |
C22832
|
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 Penthièvre Context triple: [Louis Jean Marie de Bourbon, Duke of Penthièvre, instanceOf, Duke of Penthièvre]
-
A.
Duke of Richmond
The Duke of Richmond is a hereditary noble title in the Peerage of England, historically granted to members of the royal family or high-ranking aristocrats associated with the region of Richmond.
-
B.
Duke of Bourbon
The Duke of Bourbon is a noble title historically held by members of the French royal House of Bourbon, signifying high-ranking aristocratic status, territorial lordship, and close proximity to the French crown.
-
C.
Duke of Brittany
The Duke of Brittany was the sovereign or semi-sovereign ruler of the historical Duchy of Brittany in western France, holding feudal authority, managing regional governance, and often navigating complex political relations with the French crown and neighboring powers.
-
D.
Duke of Fife
The Duke of Fife is a hereditary title in the Peerage of the United Kingdom, traditionally associated with the Fife region of Scotland and historically granted to members of the British royal family or their close relatives.
-
E.
Duke of Lancaster
The Duke of Lancaster is a noble title in the Peerage of England historically associated with the ruling monarch and the administration of the Duchy of Lancaster, a royal estate providing independent income to the sovereign.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 4:11 p.m.