Triple
T8466423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of the Gulf |
E200173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Union Army department |
C1992
|
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 department Context triple: [Department of the Gulf, instanceOf, Union Army department]
-
A.
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.
-
B.
U.S. Army regiment
A U.S. Army regiment is a traditional military unit designation that historically grouped multiple battalions or companies under a common lineage and identity, now used primarily for organizational, administrative, and ceremonial purposes rather than as a primary tactical formation.
-
C.
Confederate Army general
A Confederate Army general was a high-ranking military officer who commanded Confederate forces during the American Civil War, overseeing strategy, operations, and troops in support of the secessionist Southern states.
-
D.
U.S. Army battalion
A U.S. Army battalion is a mid-sized tactical unit, typically consisting of 300–1,000 soldiers organized into several companies, capable of independent operations under a battalion commander.
-
E.
United States Army command
chosen
The United States Army command is the organizational structure and authority framework responsible for directing, coordinating, and controlling Army forces and operations to accomplish national defense 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:11 p.m.