Triple
T29423121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11 Engineer Company |
E746207
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combat engineer company |
C55588
|
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: combat engineer company Context triple: [11 Engineer Company, instanceOf, combat engineer company]
-
A.
armored engineer battalion
An armored engineer battalion is a military unit that combines combat engineering capabilities with armored vehicles to conduct mobility, counter-mobility, and survivability operations in support of mechanized and armored forces.
-
B.
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.
-
C.
army engineer
An army engineer is a military specialist who designs, constructs, and maintains infrastructure and systems to support combat operations and logistical needs in diverse and often hostile environments.
-
D.
civil engineer squadron
A civil engineer squadron is a military unit responsible for planning, constructing, maintaining, and repairing infrastructure and facilities to support operational readiness and base sustainability.
-
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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:07 p.m.