Triple
T26031328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Air Force engineering system |
E647437
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military engineering system |
C50161
|
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 system Context triple: [Royal Air Force engineering system, instanceOf, military engineering system]
-
A.
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.
-
B.
military architecture
Military architecture is the specialized design and construction of fortifications, defensive structures, and related military facilities intended to protect territories, control strategic points, and withstand or conduct armed attacks.
-
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.
military fortification system
A military fortification system is an integrated network of defensive structures, obstacles, and support facilities designed to protect territory, forces, and strategic assets from enemy attack.
-
E.
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.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:06 a.m.