Triple

T21378813
Position Surface form Disambiguated ID Type / Status
Subject Albert, Duke of Prussia E527286 entity
Predicate instanceOf P0 FINISHED
Object former Grand Master of the Teutonic Order C33219 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: former Grand Master of the Teutonic Order
Context triple: [Albert, Duke of Prussia, instanceOf, former Grand Master of the Teutonic Order]
  • A. Grand Master of the Teutonic Order chosen
    The Grand Master of the Teutonic Order is the supreme head of the medieval Catholic military-religious order, overseeing its spiritual mission, military campaigns, territorial governance, and internal administration.
  • B. Grand Master of the Knights Hospitaller
    The Grand Master of the Knights Hospitaller is the supreme leader and chief administrator of the Order, responsible for its spiritual direction, military command, and governance of its territories and members.
  • C. Grand Master of the Knights Templar
    The Grand Master of the Knights Templar is the supreme leader of the order, responsible for guiding its spiritual mission, military campaigns, and administrative governance across all its territories.
  • D. 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.
  • E. Grand Duke of Lithuania
    The Grand Duke of Lithuania was the sovereign ruler of the Grand Duchy of Lithuania, holding supreme political, military, and judicial authority over its territories and often engaging in dynastic unions with neighboring states.
  • F. None of above.

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_69e0b51f363c8190944000ab5523b02b completed April 16, 2026, 10:08 a.m.
Created at: April 16, 2026, 5:11 p.m.