Triple
T35860827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Northeastern Virginia |
E1036942
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Union Army military department |
C66121
|
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 military department Context triple: [Department of Northeastern Virginia, instanceOf, Union Army military department]
-
A.
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.
-
B.
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.
-
C.
Union Army operation
A Union Army operation is a coordinated military action or campaign conducted by Union forces during the American Civil War to achieve specific strategic or tactical objectives.
-
D.
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.
-
E.
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.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.