Triple
T37703376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tidball’s Battery |
E939127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Union Army artillery battery |
C66389
|
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 artillery battery Context triple: [Tidball’s Battery, instanceOf, Union Army artillery battery]
-
A.
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.
-
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 fortification
A Union Army fortification is a defensive military structure, such as an earthwork, fort, or entrenchment, constructed and used by United States forces during the Civil War to protect troops, control territory, and support offensive and defensive operations.
-
D.
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.
-
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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.