Triple
T26836070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Mahan |
E675634
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Union Army fortification |
C52100
|
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: Union Army fortification Context triple: [Fort Mahan, instanceOf, Union Army fortification]
-
A.
Union Army logistics operation
A Union Army logistics operation is the coordinated planning, procurement, transportation, and distribution of supplies, equipment, and personnel to sustain Union forces during the American Civil War.
-
B.
Confederate home guard
The Confederate home guard was a local militia force in the Confederate States during the American Civil War, composed mainly of men exempt from regular military service, tasked with maintaining order, defending home fronts, and enforcing conscription laws.
-
C.
Union Army
The Union Army was the land-based military force of the United States (the Union) during the American Civil War, responsible for fighting the Confederate States and preserving the nation.
-
D.
Union Army field army
A Union Army field army was a large, operational-level Civil War military formation composed of multiple corps and supporting units, organized to conduct sustained campaigns and major battles for the United States.
-
E.
Union Army infantry division
A Union Army infantry division was a mid-level Civil War combat formation composed of multiple infantry brigades, supporting artillery, and staff, organized to conduct sustained offensive and defensive operations under a divisional commander.
- F. None of above. chosen
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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:04 a.m.