Triple
T13742565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles, Cardinal of Lorraine |
E330121
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | House of Guise member |
C22771
|
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 Guise member Context triple: [Charles, Cardinal of Lorraine, instanceOf, House of Guise member]
-
A.
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.
-
B.
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.
-
C.
member of the House of Lorraine
chosen
A member of the House of Lorraine is an individual belonging by birth or legitimate descent to the historic European noble dynasty that ruled the Duchy of Lorraine and later held significant royal and imperial titles.
-
D.
member of the House of Bourbon
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.
member of the House of La Tour d’Auvergne
A member of the House of La Tour d’Auvergne is an individual belonging by birth or marriage to this historic French noble family, noted for its prominent political, military, and ecclesiastical roles in European history.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:55 p.m.