Triple
T30937005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaffin’s Bluff defenses |
E788148
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate fortification system |
C59565
|
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 fortification system Context triple: [Chaffin’s Bluff defenses, instanceOf, Confederate fortification system]
-
A.
Confederate defensive position
chosen
A Confederate defensive position is a fortified location established by Confederate forces during the American Civil War to resist Union attacks and control key terrain or strategic points.
-
B.
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.
-
C.
Union Army fortification
A Union Army fortification is a defensive military structure, such as an earthwork, fort, or entrenchment, constructed and used by United States forces during the Civil War to protect troops, control territory, and support offensive and defensive operations.
-
D.
Union Army fort
A Union Army fort is a fortified military installation constructed and used by United States forces during the Civil War to defend strategic locations, house troops, and support offensive and defensive operations.
-
E.
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.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:52 p.m.