Triple
T7586357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil War Defenses of Washington |
E179621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic military fortification 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: historic military fortification network Context triple: [Civil War Defenses of Washington, instanceOf, historic military fortification network]
-
A.
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.
-
B.
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.
-
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.
historic coastal fort
A historic coastal fort is a fortified structure built along a shoreline to defend strategic waterways and harbors from naval threats, often featuring thick masonry walls, artillery emplacements, and commanding views of the sea.
-
E.
historic infrastructure
Historic infrastructure comprises long-standing physical structures and systems—such as bridges, roads, canals, and railways—that were built in the past and continue to embody cultural, technological, and architectural significance.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 3:52 p.m.