Triple
T14053763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Charles Henry Friso |
E338158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hereditary 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: hereditary stadtholder of the Netherlands Context triple: [William Charles Henry Friso, instanceOf, hereditary stadtholder of the Netherlands]
-
A.
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.
-
B.
overlord of the Burgundian Netherlands
The overlord of the Burgundian Netherlands is the supreme feudal ruler who holds ultimate political and legal authority over the patchwork of duchies, counties, and lordships that make up the Burgundian-controlled Low Countries.
-
C.
Dutch regent
A Dutch regent was a member of the wealthy urban patrician elite who governed cities and provinces in the Dutch Republic, often holding multiple civic offices and exerting significant political and economic influence.
-
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.
Dutch royal
A Dutch royal is a member of the Netherlands' reigning House of Orange-Nassau, holding constitutional, ceremonial, and representative roles within the Dutch monarchy.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:20 p.m.