Triple

T37091612
Position Surface form Disambiguated ID Type / Status
Subject Karl Anton, Prince of Hohenzollern E918435 entity
Predicate instanceOf P0 FINISHED
Object Prince of Hohenzollern C65566 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: Prince of Hohenzollern
Context triple: [Karl Anton, Prince of Hohenzollern, instanceOf, Prince of Hohenzollern]
  • A. Duke of Prussia
    The Duke of Prussia was a hereditary noble title held by the rulers of the Duchy of Prussia, originally a fief of the Polish Crown that later became the core territory of the Kingdom of Prussia.
  • B. Grand Duke of Mecklenburg-Schwerin
    The Grand Duke of Mecklenburg-Schwerin was the hereditary sovereign ruler of the Grand Duchy of Mecklenburg-Schwerin, a German state within the Holy Roman Empire and later the German Confederation and German Empire, until the monarchy’s abolition in 1918.
  • C. King in Prussia
    King in Prussia was the royal title used by the Hohenzollern rulers of Brandenburg-Prussia from 1701 to 1772, signifying their kingship over Prussia while remaining nominally subordinate to the Holy Roman Emperor within the empire.
  • D. prince of Baden
    A prince of Baden is a male member of the ruling or formerly ruling noble family of the historical Grand Duchy (and earlier margraviate) of Baden in what is now southwestern Germany, typically bearing dynastic titles and succession rights within that house.
  • E. Grand Duke of Hesse
    The Grand Duke of Hesse was the hereditary sovereign ruler of the Grand Duchy of Hesse, a German state that existed from 1806 to 1918 within the Holy Roman Empire’s successor systems and later 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_69f76e9a48bc8190a3947508d8bca408 completed May 3, 2026, 3:49 p.m.
Created at: May 3, 2026, 4:14 p.m.