Triple
T20812018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louise-Christine of Savoy |
E512332
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Savoy-Carignano |
C6185
|
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: member of the House of Savoy-Carignano Context triple: [Louise-Christine of Savoy, instanceOf, member of the House of Savoy-Carignano]
-
A.
member of the House of Savoy
chosen
A member of the House of Savoy is an individual belonging by birth or marriage to the historic European royal dynasty that ruled territories including Savoy, Sardinia, and eventually unified Italy.
-
B.
member of the House of Ivrea
A member of the House of Ivrea is an individual belonging to the medieval European noble dynasty of Frankish origin that ruled or influenced several regions, including Italy and parts of France, through hereditary titles and political alliances.
-
C.
member of the House of Grimaldi
A member of the House of Grimaldi is an individual belonging by birth or lawful adoption to the historic ruling dynasty of Monaco, sharing its hereditary titles, lineage, and associated privileges.
-
D.
member of the Visconti dynasty
A member of the Visconti dynasty is an individual belonging to the powerful medieval and Renaissance noble family that ruled Milan and surrounding territories in northern Italy.
-
E.
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.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:40 p.m.