Triple
T13862859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 153rd (Leicestershire Yeomanry) Field Regiment, Royal Artillery |
E333241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Artillery regiment |
C21082
|
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: Royal Artillery regiment Context triple: [153rd (Leicestershire Yeomanry) Field Regiment, Royal Artillery, instanceOf, Royal Artillery regiment]
-
A.
artillery corps
An artillery corps is a military formation specialized in operating heavy weapons such as cannons, howitzers, and rocket systems to deliver long-range indirect fire support on the battlefield.
-
B.
artillery unit
chosen
An artillery unit is a military formation equipped with long-range weapons designed to deliver indirect fire support against enemy targets from protected or distant positions.
-
C.
British Army infantry regiment
A British Army infantry regiment is a historic, regionally or culturally affiliated military unit responsible for recruiting, training, and organizing soldiers into battalions for frontline ground combat and related duties.
-
D.
Canadian Army cavalry regiment
A Canadian Army cavalry regiment is a military unit historically composed of mounted soldiers and now typically equipped with armored vehicles, responsible for reconnaissance, security, and mobile combat operations.
-
E.
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.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:14 p.m.