Triple

T29921460
Position Surface form Disambiguated ID Type / Status
Subject Frederick William, Margrave of Brandenburg-Schwedt E759949 entity
Predicate instanceOf P0 FINISHED
Object Margrave of Brandenburg-Schwedt C56536 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: Margrave of Brandenburg-Schwedt
Context triple: [Frederick William, Margrave of Brandenburg-Schwedt, instanceOf, Margrave of Brandenburg-Schwedt]
  • A. Margrave of Meissen
    The Margrave of Meissen was a medieval and early modern noble title denoting the ruler of the Margraviate of Meissen, a key frontier principality of the Holy Roman Empire in what is now eastern Germany.
  • B. Duke of Saxony
    The Duke of Saxony is a high-ranking noble title historically held by rulers of the Saxony region in present-day Germany, signifying territorial authority, military leadership, and political influence within the Holy Roman Empire and later German states.
  • C. Prince of Anhalt-Dornburg
    A Prince of Anhalt-Dornburg was a male sovereign or co-ruling member of the small German principality of Anhalt-Dornburg within the Holy Roman Empire, holding dynastic authority over its territories and affairs.
  • D. Prince of Anhalt-Zerbst
    The Prince of Anhalt-Zerbst was the sovereign ruler of the small German principality of Anhalt-Zerbst within the Holy Roman Empire, holding dynastic, political, and territorial authority over its lands and subjects.
  • E. 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.
  • 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_69f2246189fc8190996b63ee1f9a2374 completed April 29, 2026, 3:31 p.m.
Created at: April 29, 2026, 6:14 p.m.