Triple
T33269780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combahee River Raid |
E851745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Union Army operation |
C61662
|
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 operation Context triple: [Combahee River Raid, instanceOf, Union Army operation]
-
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.
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.
-
C.
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.
-
D.
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.
-
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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:32 a.m.