Triple
T21997685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Defence Service of Engineers |
E543247
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military engineering cadre |
C39173
|
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: military engineering cadre Context triple: [Indian Defence Service of Engineers, instanceOf, military engineering cadre]
-
A.
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.
-
B.
military engineering tradition
A military engineering tradition is the historically developed body of practices, knowledge, values, and institutional norms that guide how a society designs, constructs, and employs engineering solutions for military purposes across time.
-
C.
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.
-
D.
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.
-
E.
corps of engineers
chosen
A corps of engineers is an organized body of military or civilian engineers responsible for planning, designing, constructing, and maintaining infrastructure and technical projects, often in support of national defense or public works.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:19 p.m.