Triple
T1752496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George William, Duke of Brunswick-Lüneburg |
E38475
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Brunswick-Lüneburg |
C7687
|
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 Brunswick-Lüneburg Context triple: [George William, Duke of Brunswick-Lüneburg, instanceOf, Duke of Brunswick-Lüneburg]
-
A.
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.
-
B.
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.
-
C.
Prince of Orange
The Prince of Orange is a hereditary noble title historically associated with the sovereign rulers of the Principality of Orange and later with the heir apparent to the Dutch throne.
-
D.
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.
-
E.
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.
- 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_69a8862bdb2081908aefe831c8aa8017 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:31 p.m.