Triple

T2386622
Position Surface form Disambiguated ID Type / Status
Subject Władysław IV Vasa E48838 entity
Predicate instanceOf P0 FINISHED
Object member of the House of Vasa C11503 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 Vasa
Context triple: [Władysław IV Vasa, instanceOf, member of the House of Vasa]
  • A. 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.
  • B. 17th-century Swedish monarch
    A 17th-century Swedish monarch is a sovereign ruler of Sweden during the 1600s who governed the kingdom’s political, military, and religious affairs amid major European conflicts and internal state-building.
  • C. member of the House of Holstein-Gottorp-Romanov
    A member of the House of Holstein-Gottorp-Romanov is an individual belonging to the German-Russian dynastic branch that ruled the Russian Empire from Peter III through the last tsars, combining Holstein-Gottorp and Romanov lineage.
  • D. member of the House of Romanov
    A member of the House of Romanov is an individual belonging by birth or marriage to the former imperial dynasty that ruled Russia from 1613 until the abdication of Tsar Nicholas II in 1917.
  • E. Swedish count
    A Swedish count is a noble title in Sweden, historically ranking below a duke and above a baron, often associated with hereditary privileges, land ownership, and social status within the Swedish aristocracy.
  • 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_69a88aa5f63081908d07fd302029fcbd completed March 4, 2026, 7:40 p.m.
Created at: March 4, 2026, 7:57 p.m.