Triple
T25004089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martello tower |
E625793
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century military architecture |
C30579
|
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: 19th-century military architecture Context triple: [Martello tower, instanceOf, 19th-century military architecture]
-
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.
19th-century military structure
chosen
A 19th-century military structure is a fortified installation or facility designed and built during the 1800s to support, protect, and organize armed forces, often reflecting the era’s evolving technologies, tactics, and geopolitical needs.
-
C.
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.
-
D.
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.
-
E.
historic military fort
A historic military fort is a fortified structure or complex built in the past for defense and military operations, often preserved today as a cultural and historical landmark.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:05 a.m.