Triple
T853025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William III of England |
E18428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Stadtholder of the Netherlands |
C2449
|
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: Stadtholder of the Netherlands Context triple: [William III of England, instanceOf, Stadtholder of the Netherlands]
-
A.
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.
-
B.
stadtholder
chosen
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.
-
C.
Dutch nobleman
A Dutch nobleman is a male member of the Netherlands' hereditary or titular nobility, historically holding social status, privileges, and often land or official positions within Dutch society.
-
D.
King of the United Kingdom
The King of the United Kingdom is the hereditary sovereign and head of state who performs constitutional, ceremonial, and representative duties for the UK and its realms.
-
E.
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.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.