Triple
T3462029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George V of Hanover |
E73046
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monarch of Hanover |
C3382
|
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: monarch of Hanover Context triple: [George V of Hanover, instanceOf, monarch of Hanover]
-
A.
King of Hanover
chosen
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.
monarch of England
A monarch of England is the sovereign head of state who holds the highest hereditary authority over the English realm, embodying its political continuity, legal sovereignty, and ceremonial leadership.
-
D.
Duke of Brunswick-Lüneburg
The Duke of Brunswick-Lüneburg was a title held by various princes of the Holy Roman Empire who ruled over the duchy of Brunswick-Lüneburg in what is now northern Germany, often dividing and reuniting its territories among different dynastic lines.
-
E.
Grand Duke of Hesse
The Grand Duke of Hesse was the hereditary sovereign ruler of the Grand Duchy of Hesse, a German state that existed from 1806 to 1918 within the Holy Roman Empire’s successor systems and later the German Empire.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:17 p.m.