Triple
T20616705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lee's second invasion of the North |
E506586
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate offensive |
C34265
|
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 offensive Context triple: [Lee's second invasion of the North, instanceOf, Confederate offensive]
-
A.
Union offensive
Union offensive refers to the coordinated series of military campaigns and strategic initiatives launched by the Union during the American Civil War to weaken, divide, and ultimately defeat the Confederacy.
-
B.
British offensive
A British offensive is a coordinated military campaign initiated by British armed forces to attack and weaken enemy positions, gain territory, or achieve specific strategic objectives.
-
C.
post–Civil War Southern campaign
A post–Civil War Southern campaign is a coordinated political, social, or military effort undertaken in the American South after 1865 to shape Reconstruction outcomes, reassert regional power, or influence national policy and public opinion.
-
D.
land offensive
chosen
A land offensive is a coordinated, large-scale military operation conducted primarily by ground forces to seize territory, defeat enemy formations, or achieve strategic objectives on land.
-
E.
American Civil War military raid
An American Civil War military raid is a swift, targeted incursion by Union or Confederate forces—often cavalry or small detachments—conducted behind enemy lines to disrupt communications, supply lines, infrastructure, or morale without seeking to hold territory.
- 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:41 a.m.