Triple
T28379602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knock John Fort |
E718854
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II military fortification |
C876
|
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: World War II military fortification Context triple: [Knock John Fort, instanceOf, World War II military fortification]
-
A.
military fortification system
chosen
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.
-
B.
World War II site
A World War II site is a historically significant location directly associated with events, operations, or impacts of the Second World War, preserved or recognized for its cultural, military, or memorial value.
-
C.
Cold War military site
A Cold War military site is a strategically located facility, installation, or complex developed or used during the Cold War era for defense, surveillance, weapons deployment, command and control, or related military operations shaped by nuclear deterrence and superpower rivalry.
-
D.
former military complex
A former military complex is a decommissioned installation once used for defense or armed forces operations, now repurposed, abandoned, or awaiting redevelopment.
-
E.
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.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:05 a.m.