Triple
T37249290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch school of military engineering |
E923945
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | school of fortification design |
C44362
|
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: school of fortification design Context triple: [Dutch school of military engineering, instanceOf, school of fortification design]
-
A.
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.
-
B.
military engineering tradition
chosen
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.
military engineering system
A military engineering system is an integrated framework of technologies, processes, and organizational structures designed to plan, construct, maintain, and protect military infrastructure and capabilities in support of defense operations.
-
D.
work on siegecraft
A work on siegecraft is a treatise or manual that systematically explains the principles, techniques, and technologies used to attack, defend, and fortify positions during sieges.
-
E.
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.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.