Triple
T22015785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | François de Rohan, Prince de Soubise |
E543704
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prince of Soubise |
C45669
|
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: prince of Soubise Context triple: [François de Rohan, Prince de Soubise, instanceOf, prince of Soubise]
-
A.
Duke of Montpensier
The Duke of Montpensier is a French noble title historically held by junior branches of the royal House of Bourbon, often associated with significant political influence, military service, and extensive landed estates.
-
B.
Duke of Vendôme
The Duke of Vendôme is a noble title historically associated with the French peerage, often held by prominent members of the Bourbon-Vendôme branch of the royal family.
-
C.
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.
-
D.
Marquis of Provence
The Marquis of Provence is a noble title historically granted to the feudal ruler of the borderland region of Provence, responsible for its military defense, administration, and representation within the broader realm.
-
E.
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.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:22 p.m.