Triple
T30888733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Harrison sector |
E786837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Civil War military sector |
C43649
|
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: Civil War military sector Context triple: [Fort Harrison sector, instanceOf, Civil War military sector]
-
A.
military sector
The military sector encompasses organizations, resources, and activities dedicated to national defense, security operations, and the development and deployment of armed forces and related technologies.
-
B.
civil war theatre
chosen
A civil war theatre is a defined geographic region or operational domain within a civil war where military, political, and social conflicts are concentrated and coordinated.
-
C.
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.
-
D.
war economy
A war economy is an economic system in which a nation’s resources, production, and policies are heavily directed toward supporting military conflict, often involving central planning, rationing, and reallocation of labor and capital from civilian to defense needs.
-
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.
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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:49 p.m.