Triple

T20748246
Position Surface form Disambiguated ID Type / Status
Subject Joachim Frederick, Elector of Brandenburg E510644 entity
Predicate successorAsDukeOfPrussia P141349 FINISHED
Object John Sigismund, Elector of Brandenburg NE NERFINISHED

How this triple was built (3 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: John Sigismund, Elector of Brandenburg | Statement: [Joachim Frederick, Elector of Brandenburg, successorAsDukeOfPrussia, John Sigismund, Elector of Brandenburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: John Sigismund, Elector of Brandenburg
Context triple: [Joachim Frederick, Elector of Brandenburg, successorAsDukeOfPrussia, John Sigismund, Elector of Brandenburg]
  • A. John Sigismund, Elector of Brandenburg chosen
    John Sigismund, Elector of Brandenburg, was an early 17th-century German prince of the Hohenzollern dynasty whose inheritance of Prussia and other territories significantly expanded and shaped the future Kingdom of Prussia.
  • B. Joachim Frederick, Elector of Brandenburg
    Joachim Frederick, Elector of Brandenburg, was a late 16th- and early 17th-century German prince of the Hohenzollern dynasty who expanded his power by uniting the Electorate of Brandenburg with the Duchy of Prussia under his rule.
  • C. Joachim II Hector, Elector of Brandenburg
    Joachim II Hector was a 16th-century Elector of Brandenburg known for consolidating Hohenzollern power, navigating the Reformation by adopting Lutheranism while retaining some Catholic practices, and strengthening his territory’s political and economic position within the Holy Roman Empire.
  • D. John George, Elector of Brandenburg
    John George, Elector of Brandenburg, was a 16th-century German prince of the Hohenzollern dynasty who ruled Brandenburg during the early Reformation era and helped shape its political and religious course within the Holy Roman Empire.
  • E. Frederick III, Elector of Brandenburg
    Frederick III, Elector of Brandenburg (later King Frederick I in Prussia) was a late 17th-century German prince who elevated Brandenburg-Prussia to a kingdom and laid foundations for the rise of Prussia as a European power.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successorAsDukeOfPrussia
Context triple: [Joachim Frederick, Elector of Brandenburg, successorAsDukeOfPrussia, John Sigismund, Elector of Brandenburg]
  • A. successorAsKingOfPrussia
    Indicates that one person became the next king of Prussia following another person.
  • B. predecessorAsDukeOfPrussia
    Indicates that one entity previously held the title of Duke of Prussia immediately before another entity.
  • C. successorAsDukeOfSilesia
    Indicates that one entity became the next holder of the title Duke of Silesia after another entity, succeeding them in that ducal position.
  • D. successorAsHighDukeOfPoland
    Indicates that one entity became the next holder of the title High Duke of Poland after another entity, succeeding them in that position.
  • E. successorAsDukeOfSaxony
    Indicates that one entity became the next Duke of Saxony following another entity in succession.
  • F. None of above. chosen

Provenance (4 batches)

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_69e0b4c845e88190b4c5f3ae79291182 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c226fbf881909794eff3ee9e206b completed April 21, 2026, 12:17 a.m.
PD Predicate disambiguation batch_69e5c0509608819080cdbf47fcddfe36 completed April 20, 2026, 5:57 a.m.
PDg Predicate description generation batch_69e5c3cbe5788190b7ace43bfdac2ef6 completed April 20, 2026, 6:12 a.m.
Created at: April 16, 2026, 12:33 p.m.