Triple
T20063616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birney's Division |
E499549
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Union Army infantry division |
C42802
|
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 infantry division Context triple: [Birney's Division, instanceOf, Union Army infantry division]
-
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.
Confederate States Army unit
A Confederate States Army unit is an organized military formation, such as a regiment, battalion, or company, that served under the Confederate States of America during the American Civil War.
-
C.
U.S. Army infantry division
A U.S. Army infantry division is a large, combined-arms military formation, typically consisting of several brigades and supporting units, organized and equipped primarily for ground combat operations centered on infantry forces.
-
D.
U.S. Army National Guard division
A U.S. Army National Guard division is a large, state-based military formation that can be federally mobilized, combining multiple brigades and support units to conduct sustained combat and support operations alongside active-duty Army forces.
-
E.
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.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:39 p.m.