Triple
T25554620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeomanry |
E640535
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | volunteer cavalry force |
C39819
|
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: volunteer cavalry force Context triple: [Yeomanry, instanceOf, volunteer cavalry force]
-
A.
paramilitary volunteer
A paramilitary volunteer is an individual who voluntarily joins and participates in an organized, non-regular armed group that operates with military-style structure, training, or tactics, often in support of or parallel to official security forces.
-
B.
auxiliary military force
An auxiliary military force is a supplementary, often non-regular or part-time armed organization that supports a nation’s primary military through additional manpower, specialized skills, or local defense roles.
-
C.
British volunteer defence force
chosen
A British volunteer defence force is a non-regular, citizen-based military organization formed to supplement the professional armed forces in times of war, crisis, or national emergency.
-
D.
Parliamentarian cavalry
Parliamentarian cavalry were mounted troops loyal to the English Parliament during the Civil War, combining mobility, shock tactics, and disciplined formations to challenge Royalist forces on the battlefield.
-
E.
irregular military forces
Irregular military forces are non-state or semi-organized armed groups that operate outside formal national military structures, often using unconventional tactics and lacking official recognition as regular armed forces.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 3:38 p.m.