Triple
T37845386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | defences of Port Mahón |
E943585
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military defensive network |
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: military defensive network Context triple: [defences of Port Mahón, instanceOf, military defensive network]
-
A.
military base network
A military base network is an interconnected system of communication, data, and operational infrastructure linking facilities, units, and resources across one or more military installations to support command, control, logistics, and security functions.
-
B.
military-security structure
A military-security structure is an organized system of forces, institutions, and mechanisms designed to protect a state or entity from external and internal threats through defense, intelligence, and enforcement capabilities.
-
C.
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.
-
D.
border defense system
A border defense system is an integrated network of physical barriers, surveillance technologies, personnel, and response protocols designed to monitor, control, and protect a nation's boundaries from unauthorized crossings and external threats.
-
E.
military training infrastructure network
A military training infrastructure network is an integrated system of facilities, ranges, technologies, and support services designed to plan, deliver, and sustain training activities for armed forces across multiple locations.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.