Triple

T4274296
Position Surface form Disambiguated ID Type / Status
Subject Frederick William, Duke of Courland E97010 entity
Predicate instanceOf P0 FINISHED
Object member of the House of Kettler C15472 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 Kettler
Context triple: [Frederick William, Duke of Courland, instanceOf, member of the House of Kettler]
  • A. member of the House of Hesse-Darmstadt
    A member of the House of Hesse-Darmstadt is an individual belonging by birth or marriage to the German princely dynasty that historically ruled the Landgraviate and later Grand Duchy of Hesse-Darmstadt.
  • B. member of the House of Wettin
    A member of the House of Wettin is an individual belonging to the historic German noble and royal dynasty that ruled various central European territories, including Saxony and Poland, over many centuries.
  • C. member of the House of Württemberg
    A member of the House of Württemberg is an individual belonging by birth or lawful adoption to the historic German noble and royal dynasty that ruled the region of Württemberg and its predecessor territories.
  • D. member of the House of Holstein-Gottorp
    A member of the House of Holstein-Gottorp is an individual belonging to a cadet branch of the Oldenburg dynasty that ruled or influenced territories in northern Germany, Scandinavia, and Russia through dynastic unions and successions.
  • E. House of Hohenzollern member
    A House of Hohenzollern member is an individual belonging by birth or legitimate adoption to the historic German noble and royal dynasty that ruled territories including Brandenburg-Prussia and the German Empire.
  • 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_69b34544be3c819084d1ab82d29f90c5 completed March 12, 2026, 10:59 p.m.
Created at: March 12, 2026, 11:07 p.m.