Triple
T9552408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conrad II, Holy Roman Emperor |
E230453
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Salian dynasty |
C26001
|
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 Salian dynasty Context triple: [Conrad II, Holy Roman Emperor, instanceOf, member of the Salian dynasty]
-
A.
Capetian dynasty member
A Capetian dynasty member is an individual belonging by blood or legitimate descent to the royal house founded by Hugh Capet, which ruled France and various European realms from the late 10th century onward.
-
B.
Carolingian dynasty member
A Carolingian dynasty member is an individual belonging to the Frankish royal family that ruled large parts of Western and Central Europe from the 8th to 10th centuries, originating with Charles Martel and reaching its height under Charlemagne.
-
C.
House of Hohenstaufen member
A House of Hohenstaufen member is an individual belonging to the medieval German noble dynasty that produced several Holy Roman Emperors and kings of Germany, Italy, and Sicily between the 12th and 13th centuries.
-
D.
member of the House of Welf
A member of the House of Welf is an individual belonging by birth or legitimate adoption to the historic European noble dynasty known as the Welfs, which has produced numerous dukes, princes, and monarchs.
-
E.
member of the Billung dynasty
A member of the Billung dynasty is an individual belonging to the medieval German noble family that held significant ducal power in Saxony from the 10th to early 12th 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:02 p.m.