Triple
T14639347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish Maquis |
E343682
|
entity |
| Predicate | hasEnemy |
P4675
|
FINISHED |
| Object | Francoist security forces |
—
|
NE GENERATED |
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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Francoist security forces Context triple: [Spanish Maquis, hasEnemy, Francoist security forces]
-
A.
Francoist military forces
chosen
Francoist military forces were the armed units loyal to General Francisco Franco that fought for and upheld his authoritarian regime during and after the Spanish Civil War.
-
B.
Spanish Republican security forces
The Spanish Republican security forces were the law enforcement and public order agencies loyal to the Second Spanish Republic during the Spanish Civil War, encompassing units such as the Assault Guard and other police and security corps.
-
C.
Spanish royalist army
The Spanish royalist army was the military force loyal to the Spanish Crown that fought to suppress independence movements and maintain colonial rule in territories such as New Spain during the early 19th century.
-
D.
People's Republican Army
The People's Republican Army was a military force aligned with the Spanish Republic during the Spanish Civil War, known for participating in key engagements such as the Battle of Guadalajara.
-
E.
Spanish Republican Army
The Spanish Republican Army was the military force loyal to the democratically elected Second Spanish Republic during the Spanish Civil War, fighting primarily against Franco’s Nationalist forces and their foreign allies.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:26 a.m.