Triple
T839380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michiel de Ruyter |
E18142
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch admiral |
C192
|
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: Dutch admiral Context triple: [Michiel de Ruyter, instanceOf, Dutch admiral]
-
A.
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.
-
B.
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.
-
C.
naval officer
chosen
A naval officer is a commissioned leader in a navy responsible for commanding personnel and vessels, making strategic and tactical decisions, and ensuring the effective operation and readiness of maritime forces.
-
D.
Prince of Orange
The Prince of Orange is a hereditary noble title historically associated with the sovereign rulers of the Principality of Orange and later with the heir apparent to the Dutch throne.
-
E.
stadtholder
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.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.