Triple
T38100809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 60th (2/2nd London) Division |
E951371
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Territorial Force division |
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 division Context triple: [60th (2/2nd London) Division, instanceOf, Territorial Force division]
-
A.
Territorial Force formation
chosen
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.
Territorial Army battalion
A Territorial Army battalion is a reserve military unit composed of part-time volunteer soldiers who train periodically and can be mobilized to support regular forces in national defense, security operations, and emergencies.
-
C.
Australian Imperial Force unit
An Australian Imperial Force unit is a military formation composed of Australian volunteer soldiers raised for overseas service during World War I under the Australian Imperial Force organization.
-
D.
U.S. Army National Guard division
A U.S. Army National Guard division is a large, state-based military formation that can be federally mobilized, combining multiple brigades and support units to conduct sustained combat and support operations alongside active-duty Army forces.
-
E.
regional military unit
A regional military unit is an organized group of armed forces assigned to operate within a specific geographic area, responsible for defense, security, and military operations in that region.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.