Triple
T32498825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petersburg fortifications |
E830596
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Civil War battlefield fortifications |
C11829
|
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: Civil War battlefield fortifications Context triple: [Petersburg fortifications, instanceOf, Civil War battlefield fortifications]
-
A.
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.
-
B.
Civil War site
chosen
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.
-
C.
civil war theatre
A civil war theatre is a defined geographic region or operational domain within a civil war where military, political, and social conflicts are concentrated and coordinated.
-
D.
Confederate defensive position
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.
-
E.
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.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:59 a.m.