Triple
T7625903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's Own Oxfordshire Hussars |
E172630
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yeomanry regiment |
C2497
|
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: Yeomanry regiment Context triple: [Queen's Own Oxfordshire Hussars, instanceOf, Yeomanry regiment]
-
A.
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.
-
B.
British East India Company regiment
A British East India Company regiment was a military unit raised, organized, and maintained by the Company in India to protect its commercial interests, enforce territorial control, and support colonial governance.
-
C.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
D.
British Army organizational element
A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
-
E.
Prussian Army regiment
A Prussian Army regiment is a military unit of the Kingdom of Prussia, typically composed of several battalions or squadrons, organized under a unified command structure for tactical, administrative, and ceremonial purposes.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:56 p.m.