Triple
T32409460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herman II, Duke of Swabia |
E828177
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Conradine dynasty |
C34523
|
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 Conradine dynasty Context triple: [Herman II, Duke of Swabia, instanceOf, member of the Conradine dynasty]
-
A.
Conradine dynasty member
chosen
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.
-
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 Brunonen dynasty
A member of the Brunonen dynasty is an individual belonging to a medieval German noble family that held significant territorial and political influence in Saxony and surrounding regions during the 10th and 11th centuries.
-
D.
member of the Salian dynasty
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.
-
E.
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.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:53 a.m.