Triple
T891599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick I of Prussia |
E19250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Elector of Brandenburg |
C1441
|
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: Elector of Brandenburg Context triple: [Frederick I of Prussia, instanceOf, Elector of Brandenburg]
-
A.
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.
-
B.
prince-electorate
chosen
A prince-electorate is a sovereign or semi-sovereign ruler within the Holy Roman Empire who held the hereditary right to participate in the election of the emperor.
-
C.
King of Hanover
The King of Hanover was the hereditary monarch and head of state of the Kingdom of Hanover, a German kingdom that existed from 1814 to 1866, ruling over its government, military, and foreign affairs.
-
D.
Governor-General of the Habsburg Netherlands
The Governor-General of the Habsburg Netherlands was the monarch’s chief representative who governed the provinces on behalf of the Habsburg ruler, overseeing administration, military affairs, and the implementation of imperial policy.
-
E.
stadtholder
A stadtholder was a provincial governor or chief executive in the Dutch Republic, serving as the representative of the sovereign or the States and often combining military and political leadership.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.