Triple
T18788232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederate defenses of Mobile |
E459436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate States Army 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: Confederate States Army fortification network Context triple: [Confederate defenses of Mobile, instanceOf, Confederate States Army fortification network]
-
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.
line of fortifications
A line of fortifications is a connected series of defensive structures, such as walls, trenches, and strongpoints, designed to protect a territory or position by forming a continuous or coordinated barrier against attack.
-
C.
Civil War site
A Civil War site is a historically significant location where events related to the American Civil War occurred, such as battles, encampments, or military operations, and is preserved or recognized for its cultural and educational value.
-
D.
Civil War–era cannon
A Civil War–era cannon is a large, muzzle-loading artillery piece, typically made of cast iron or bronze, used during the American Civil War to fire solid shot, explosive shells, or canister at enemy troops and fortifications.
-
E.
military confederacy
A military confederacy is a loose alliance of semi-independent states or groups that coordinate their armed forces and defense policies for mutual security while retaining significant political autonomy.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:53 a.m.