Triple
T8232026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mando de Personal |
E192315
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | órgano del Ejército de Tierra de España |
C298
|
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: órgano del Ejército de Tierra de España Context triple: [Mando de Personal, instanceOf, órgano del Ejército de Tierra de España]
-
A.
Spanish Air Force institution
The Spanish Air Force institution is the national military aviation organization of Spain responsible for defending the country’s airspace, conducting aerial operations, and supporting national and international security missions.
-
B.
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.
-
C.
military organization
chosen
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
D.
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.
-
E.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:46 p.m.