Triple
T10886930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 52nd (Lowland) Infantry Division |
E257072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Territorial Force formation |
C28950
|
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 Force formation Context triple: [52nd (Lowland) Infantry Division, instanceOf, Territorial Force formation]
-
A.
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.
-
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.
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.
-
D.
Canadian Expeditionary Force formation
A Canadian Expeditionary Force formation is an organized military unit or grouping, such as a battalion, brigade, or division, raised by Canada for overseas service during the First World War.
-
E.
Indian Armed Forces formation
An Indian Armed Forces formation is an organized military unit or grouping, such as a command, corps, division, brigade, or equivalent structure, established to plan, coordinate, and conduct operations within the Indian Army, Navy, or Air Force.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:21 p.m.