Triple
T34330183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savage’s Station on the Richmond and York River Railroad |
E880981
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Union Army supply depot |
C38998
|
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 supply depot Context triple: [Savage’s Station on the Richmond and York River Railroad, instanceOf, Union Army supply depot]
-
A.
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.
-
B.
Union Army fort
A Union Army fort is a fortified military installation constructed and used by United States forces during the Civil War to defend strategic locations, house troops, and support offensive and defensive operations.
-
C.
Union Army logistics operation
chosen
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.
Union Army training camp
A Union Army training camp was a temporary Civil War-era military installation where Northern volunteers and conscripts were organized, drilled, equipped, and prepared for combat before deployment to the front.
-
E.
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.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:58 a.m.