Triple
T16301493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Henry of the Netherlands (1820–1879) |
E395799
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch military officer |
C7361
|
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 military officer Context triple: [Prince Henry of the Netherlands (1820–1879), instanceOf, Dutch military officer]
-
A.
Dutch general
chosen
A Dutch general is a high-ranking military officer from the Netherlands responsible for leading and overseeing major army operations, strategy, and personnel.
-
B.
Belgian general
A Belgian general is a high-ranking military officer from Belgium responsible for leading large military formations, developing strategic plans, and overseeing operations within the Belgian Armed Forces or in multinational contexts.
-
C.
Prussian general
A Prussian general is a high-ranking military officer of the historical Kingdom of Prussia, characterized by rigorous discipline, strategic planning, and leadership in organizing and commanding armies in war.
-
D.
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.
-
E.
Dutch colonial administrator
A Dutch colonial administrator is an official appointed by the Netherlands to govern, manage, and oversee political, economic, and social affairs in its overseas colonies.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:06 a.m.