Triple
T13964264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Louis, Count of Nassau-Dillenburg |
E335880
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch military commander |
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 commander Context triple: [William Louis, Count of Nassau-Dillenburg, instanceOf, Dutch military commander]
-
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.
Portuguese military commander
A Portuguese military commander is a high-ranking officer responsible for planning, directing, and overseeing military operations and personnel within Portugal’s armed forces or in joint international missions.
-
D.
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.
-
E.
Boer military leader
A Boer military leader is a commander from the Dutch-descended Afrikaner communities of South Africa who directs and organizes Boer forces in military campaigns, often characterized by mobile, guerrilla-style warfare.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:18 p.m.