Triple
T33377488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto of Worms |
E854675
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of 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 Salian dynasty Context triple: [Otto of Worms, instanceOf, member of Salian dynasty]
-
A.
member of the Salian dynasty
chosen
A member of the Salian dynasty is an individual belonging to the German royal and imperial family that ruled the Holy Roman Empire from the early 11th to mid-12th century.
-
B.
member of the Ludovingian dynasty
A member of the Ludovingian dynasty is an individual belonging to the medieval German noble house that ruled Thuringia and held significant influence in the Holy Roman Empire from the 11th to 13th centuries.
-
C.
Member of the Salian dynasty by marriage
A "Member of the Salian dynasty by marriage" is an individual who became part of the Salian royal family through a legally recognized marital union with a Salian dynasty member, rather than by blood descent.
-
D.
Conradine dynasty member
A Conradine dynasty member is an individual belonging to the early medieval German noble family that held significant power in Franconia and briefly provided a king of East Francia in the 10th century.
-
E.
member of the Constantinian dynasty
A member of the Constantinian dynasty is an individual belonging to the imperial family that ruled the Roman Empire from the rise of Constantine the Great in the early 4th century until the death of his descendants later that century.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:35 a.m.