Triple
T28478666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MADOC |
E720629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish Army organization |
C54103
|
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 Army organization Context triple: [MADOC, instanceOf, Spanish Army organization]
-
A.
Spanish military formation abroad
A Spanish military formation abroad is an organized contingent of Spain’s armed forces deployed outside national territory to conduct operations, training, peacekeeping, or support missions under national or international command.
-
B.
Spanish Army officer
A Spanish Army officer is a commissioned leader in Spain’s land forces responsible for planning, directing, and overseeing military operations, personnel, and resources in accordance with national defense policies.
-
C.
formation of the Spanish Army
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.
-
D.
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.
-
E.
Spanish Army general
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.
- F. None of above. chosen
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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:54 a.m.