Triple
T19456873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army of the Ebro |
E486756
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Republican army |
C41791
|
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: Republican army Context triple: [Army of the Ebro, instanceOf, Republican army]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Unionists in the American Civil War
Unionists in the American Civil War were individuals and groups in both Northern and Southern states who remained loyal to the United States federal government and opposed secession, supporting the preservation of the Union by political, economic, or military means.
-
E.
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.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:38 p.m.