Triple
T31041680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry I, Duke of Brabant |
E791011
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of Brabant |
C57790
|
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 Brabant Context triple: [Henry I, Duke of Brabant, instanceOf, ruler of Brabant]
-
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.
ruler of Guelders
A ruler of Guelders is the sovereign authority—such as a count, duke, or other monarch—who governed the historical territory of Guelders in the 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.
Burgundian king
A Burgundian king is the sovereign ruler of the historical Kingdom or later Duchy of Burgundy, exercising political, military, and judicial authority over its territories and people.
-
E.
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.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:59 p.m.