Triple
T20058003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queipo de Llano |
E499391
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nationalist commander |
C42798
|
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 commander Context triple: [Queipo de Llano, instanceOf, Nationalist commander]
-
A.
Georgian military commander
A Georgian military commander is a high-ranking officer from Georgia responsible for planning, directing, and overseeing military operations and strategy within the Georgian armed forces.
-
B.
Military leader
A military leader is an individual who plans, directs, and coordinates armed forces operations, making strategic and tactical decisions to achieve military objectives while managing and motivating personnel under their command.
-
C.
Nationalist Chinese military leader
A Nationalist Chinese military leader is a high-ranking officer or commander who served under the Republic of China’s Nationalist government, directing armed forces in defense of its political authority and territorial claims, often in opposition to Communist forces and foreign invaders.
-
D.
paramilitary leader
A paramilitary leader is an individual who commands, organizes, and directs a non-regular, often politically motivated armed group that operates with military-style structure, tactics, and discipline outside or alongside official state forces.
-
E.
Red Army commander
A Red Army commander is a high-ranking military officer responsible for planning, directing, and overseeing Soviet armed forces operations and personnel within the Red Army.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:38 p.m.