Triple
T2558283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army of Flanders |
E56780
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish Habsburg army |
C9650
|
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 Habsburg army Context triple: [Army of Flanders, instanceOf, Spanish Habsburg army]
-
A.
formation of the Spanish Army
chosen
The formation of the Spanish Army refers to the historical process by which Spain’s military forces evolved from medieval regional levies and royal guards into a centralized, professional national army shaped by dynastic unification, imperial expansion, and successive military reforms.
-
B.
Habsburg
Habsburg: A powerful European royal dynasty that ruled vast territories including the Holy Roman Empire, Spain, and Austria for centuries through strategic marriages and political alliances.
-
C.
institution of the Catholic Monarchy
The institution of the Catholic Monarchy is a form of early modern governance in which a monarch legitimized by Catholic doctrine wields centralized political, religious, and cultural authority over a composite realm.
-
D.
King of Aragon
The King of Aragon was the sovereign ruler of the medieval and early modern Crown of Aragon, holding authority over its constituent territories in northeastern Iberia and the Mediterranean.
-
E.
King of Castile
The King of Castile was the sovereign ruler of the medieval and early modern Kingdom of Castile on the Iberian Peninsula, holding supreme political, military, and judicial authority over its territories and subjects.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:48 p.m.