Triple
T13919113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Cunningham |
E334695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | army engineer |
C34377
|
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: army engineer Context triple: [Alexander Cunningham, instanceOf, army engineer]
-
A.
combat engineering specialty
A combat engineering specialty focuses on the tactical application of engineering skills to support military operations, including mobility, counter-mobility, survivability, and limited construction under combat conditions.
-
B.
Engineer brigade
An engineer brigade is a military unit composed of specialized engineering battalions that provide construction, mobility, counter-mobility, and survivability support to larger combat formations.
-
C.
military engineering vehicle
A military engineering vehicle is a specialized armored or unarmored platform designed to support combat operations by performing construction, demolition, obstacle breaching, and battlefield mobility or survivability tasks.
-
D.
component of land forces
A component of land forces is an organized, functionally distinct element of an army’s ground combat structure, such as infantry, armor, artillery, or support units, that contributes specific capabilities to land operations.
-
E.
German Army combat engineer battalion
A German Army combat engineer battalion is a specialized military unit that provides mobility, counter-mobility, and survivability support to combat forces through tasks such as obstacle breaching, fortification construction, route clearance, and infrastructure repair in operational environments.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.