Triple
T14333294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 56th (London) Infantry Division |
E355405
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Territorial Army formation |
C19405
|
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: Territorial Army formation Context triple: [56th (London) Infantry Division, instanceOf, Territorial Army formation]
-
A.
Territorial Force formation
A Territorial Force formation is a military organizational unit composed of part-time volunteer soldiers, structured to provide local defense and support to regular armed forces within a defined geographic area.
-
B.
Canadian Army formation
A Canadian Army formation is an organized, hierarchical grouping of military units (such as brigades or divisions) structured to conduct land operations under a unified command within the Canadian Armed Forces.
-
C.
Indian Army formation
An Indian Army formation is an organized military unit or grouping, such as a corps, division, brigade, or battalion, structured for command, control, and execution of land-based operations within the Indian Army.
-
D.
army formation
chosen
An army formation is an organized arrangement of military units and personnel on the battlefield or during maneuvers, designed to optimize command, movement, and combat effectiveness.
-
E.
New Zealand Army formation
A New Zealand Army formation is an organized military unit or grouping, such as a brigade or division, composed of personnel and equipment structured to conduct land operations under a unified command.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:13 a.m.