Triple
T8466466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Order No. 28 (New Orleans "Woman Order") |
E200174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Union Army order |
C22847
|
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 order Context triple: [General Order No. 28 (New Orleans "Woman Order"), instanceOf, Union Army order]
-
A.
Union military policy
Union military policy refers to the strategic, operational, and administrative decisions and directives that governed how the United States’ armed forces were organized, deployed, and employed to achieve national objectives during the Civil War.
-
B.
Confederate Army general
A Confederate Army general was a high-ranking military officer who commanded Confederate forces during the American Civil War, overseeing strategy, operations, and troops in support of the secessionist Southern states.
-
C.
United States Army directive
chosen
A United States Army directive is an official, authoritative order or instruction issued by Army leadership that establishes or changes policy, procedures, responsibilities, or standards for the organization.
-
D.
United States Marine Corps order
A United States Marine Corps order is an official directive issued by authorized Marine Corps leadership that prescribes policies, procedures, or actions to be followed by Marines and Marine Corps units.
-
E.
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.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:11 p.m.