Triple
T17463335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germán Gil y Yuste |
E425212
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nationalist military personnel |
C35621
|
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: Nationalist military personnel Context triple: [Germán Gil y Yuste, instanceOf, Nationalist military personnel]
-
A.
Spanish Nationalist military personnel
chosen
Spanish Nationalist military personnel are members of the armed forces who served under or supported the Nationalist faction in Spain, particularly during the Spanish Civil War and the subsequent Francoist regime.
-
B.
Polish–Lithuanian Commonwealth military personnel
Individuals who served in the armed forces of the Polish–Lithuanian Commonwealth, including its army, navy, and related military formations, from its formation in 1569 until its final partitions in the late 18th century.
-
C.
military personnel category
A military personnel category is a classification that groups service members based on roles, ranks, duties, or service status within the armed forces.
-
D.
Russian military personnel
Russian military personnel are individuals who serve in the armed forces of the Russian Federation, including its army, navy, aerospace forces, and other military branches, performing roles related to national defense, security, and military operations.
-
E.
participants in military alliance
Participants in a military alliance are sovereign states or entities that formally agree to cooperate in defense and security matters, sharing obligations, resources, and strategic commitments against common threats.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:47 a.m.