Triple
T1600702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick William, Elector of Brandenburg |
E34384
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Prussia |
C8278
|
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: Duke of Prussia Context triple: [Frederick William, Elector of Brandenburg, instanceOf, Duke of Prussia]
-
A.
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.
-
B.
King of Westphalia
The King of Westphalia was the sovereign ruler of the short-lived Kingdom of Westphalia (1807–1813), a Napoleonic client state in central Europe governed primarily by Napoleon’s brother Jérôme Bonaparte.
-
C.
King of Holland
The King of Holland is the hereditary head of state of the Netherlands, representing national unity, performing constitutional and ceremonial duties, and serving as a symbolic figure domestically and internationally.
-
D.
Elector of Hanover
The Elector of Hanover was the ruler of the Electorate of Hanover within the Holy Roman Empire, holding one of the empire’s prestigious electoral titles and, from 1714, simultaneously serving as the monarch of Great Britain.
-
E.
German Emperor
A German Emperor is the sovereign ruler who held the imperial title over the German Empire, symbolizing supreme political and military authority within the unified German state from 1871 to 1918.
- 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_69a885fdcb9c819081ce6f0b8cd477dd |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.