Triple
T24961615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reginald I, Duke of Guelders |
E624623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of Guelders |
C49346
|
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: ruler of Guelders Context triple: [Reginald I, Duke of Guelders, instanceOf, ruler of Guelders]
-
A.
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.
-
B.
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.
-
C.
King of Holland
The King of Holland is the hereditary head of state of the Netherlands, representing national unity, performing constitutional and ceremonial duties, and serving as a symbolic figure domestically and internationally.
-
D.
Duke of Lauenburg
The Duke of Lauenburg is a noble title historically associated with the ruler of the Duchy of Lauenburg, a small German principality within the Holy Roman Empire and later states of the German Confederation.
-
E.
Prince of Nassau-Usingen
The Prince of Nassau-Usingen was the sovereign ruler of the small German principality of Nassau-Usingen within the Holy Roman Empire and later the Confederation of the Rhine.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 5:59 a.m.