Triple
T27284836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis Henri, Duke of Bourbon |
E688442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | House of Condé member |
C4852
|
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: House of Condé member Context triple: [Louis Henri, Duke of Bourbon, instanceOf, House of Condé member]
-
A.
head of the House of Condé
The head of the House of Condé is the principal noble titleholder and dynastic leader of this cadet branch of the French royal Bourbon family, historically bearing political, military, and social authority within the French aristocracy.
-
B.
House of Orléans member
A House of Orléans member is an individual belonging to the cadet branch of the French royal family descended from Philippe I, Duke of Orléans, traditionally associated with significant political, dynastic, and cultural roles in French and European history.
-
C.
member of the House of Valois
A member of the House of Valois is an individual belonging to the French royal dynasty that ruled France and several related territories from the 14th to the 16th centuries.
-
D.
member of the House of Bourbon
chosen
A member of the House of Bourbon is an individual belonging by birth or legitimate descent to the historic European royal dynasty that ruled or influenced several kingdoms, including France, Spain, and Naples.
-
E.
House of Lorraine member
A House of Lorraine member is an individual belonging by birth or legitimate descent to the historic European noble dynasty that ruled Lorraine and later provided emperors, kings, and consorts to several major monarchies.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:10 a.m.