Triple

T11461365
Position Surface form Disambiguated ID Type / Status
Subject Otto I, Count of Burgundy E271667 entity
Predicate instanceOf P0 FINISHED
Object Hohenstaufen dynasty member C8657 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: Hohenstaufen dynasty member
Context triple: [Otto I, Count of Burgundy, instanceOf, Hohenstaufen dynasty member]
  • A. House of Hohenstaufen member chosen
    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.
  • B. 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.
  • C. Ottonian dynasty member
    An Ottonian dynasty member is an individual belonging to the German royal and imperial family that ruled the East Frankish (German) kingdom and Holy Roman Empire from the early 10th to early 11th centuries, beginning with Henry the Fowler and most prominently represented by Otto I, Otto II, and Otto III.
  • D. House of Habsburg member
    A House of Habsburg member is an individual belonging by birth or marriage to the historic European royal dynasty that ruled vast territories including Austria, Spain, and the Holy Roman Empire.
  • E. member of the Babenberg dynasty
    A member of the Babenberg dynasty is an individual belonging to the medieval noble family that ruled Austria and parts of Central Europe from the 10th to the mid-13th 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_69d6aae0c8d881908a5a360c0be3242e completed April 8, 2026, 7:22 p.m.
Created at: April 8, 2026, 9:35 p.m.