Triple
T6318228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don John of Austria the Younger |
E141668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish military commander |
C14970
|
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: Spanish military commander Context triple: [Don John of Austria the Younger, instanceOf, Spanish military commander]
-
A.
Spanish Army general
chosen
A Spanish Army general is a high-ranking military officer responsible for leading large army units, planning and directing operations, and advising on national defense and military strategy within Spain’s armed forces.
-
B.
Spanish colonial governor
A Spanish colonial governor was the crown-appointed official responsible for administering, defending, and representing royal authority in a designated overseas territory of the Spanish Empire.
-
C.
Mexican general
A Mexican general is a high-ranking military officer in Mexico’s armed forces responsible for leading troops, planning and executing military operations, and contributing to national defense and security strategy.
-
D.
Argentine general
An Argentine general is a high-ranking military officer in Argentina's armed forces responsible for leading large military units, planning and executing national defense strategies, and advising political authorities on security and defense matters.
-
E.
Spanish imperial military unit
A Spanish imperial military unit is an organized armed formation under the authority of the Spanish Empire, structured for conquest, defense, and control of its territories across Europe and overseas.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:29 p.m.