Triple
T23815222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shannonbridge Fortifications |
E589076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military fortification complex |
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 fortification complex Context triple: [Shannonbridge Fortifications, instanceOf, military fortification complex]
-
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.
fortified settlement
A fortified settlement is a community enclosed by defensive structures such as walls, ramparts, or palisades, designed to protect its inhabitants and resources from external threats.
-
C.
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.
-
D.
fortified building
A fortified building is a heavily constructed structure designed with defensive features such as thick walls, limited entry points, and protective battlements to resist attacks and provide security for its occupants.
-
E.
inner fortification complex
The inner fortification complex is a heavily defended core area within a larger fortified site, containing critical structures and defenses that protect the most vital personnel, resources, and command functions.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 7:58 p.m.