Triple
T7549619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contraband decision |
E178496
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Union military policy |
C22867
|
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 military policy Context triple: [Contraband decision, instanceOf, Union military policy]
-
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.
Union victory
Union victory is the successful outcome of the American Civil War for the United States (the Union), marked by the defeat of the Confederacy, preservation of the nation, and the abolition of slavery.
-
C.
military strategy
Military strategy is the high-level planning and directing of armed forces and resources to achieve political and military objectives in war or conflict.
-
D.
Napoleonic policy
Napoleonic policy refers to the strategic, administrative, legal, and military measures implemented by Napoleon Bonaparte to centralize authority, modernize state institutions, expand French influence, and consolidate his personal rule across Europe.
-
E.
United States federal government strategy
United States federal government strategy is the overarching, long-term plan and set of coordinated policies through which federal institutions define national priorities, allocate resources, and guide actions to achieve political, economic, security, and social objectives.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:49 p.m.