Triple
T15207247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berengar II of Italy |
E363420
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Ivrea |
C36286
|
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 Ivrea Context triple: [Berengar II of Italy, instanceOf, member of the House of Ivrea]
-
A.
member of the House of Savoy
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 Lorraine
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.
-
C.
member of the House of Kyburg
A member of the House of Kyburg is an individual belonging to the medieval Swiss noble dynasty that held significant territorial and political power in parts of present-day Switzerland during the High Middle Ages.
-
D.
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.
-
E.
member of the House of Alpin
A member of the House of Alpin is an individual belonging to the early medieval royal dynasty that ruled the Kingdom of the Picts and later the unified Kingdom of Scotland from the 9th to the 11th centuries.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:11 a.m.