Triple
T12727824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army of the Frontier |
E304151
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Union Army field army |
C31804
|
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 field army Context triple: [Army of the Frontier, instanceOf, Union Army field army]
-
A.
United States Army field army
A United States Army field army is a large, operational-level formation typically composed of multiple corps, organized to conduct sustained, large-scale land combat operations within a theater of war.
-
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.
branch of the Confederate States Army
A branch of the Confederate States Army is a major functional subdivision, such as infantry, cavalry, or artillery, responsible for a specific type of military operation within the Confederate land forces during the American Civil War.
-
D.
Guards field army
The Guards field army is an elite, front-line military formation composed of highly trained and well-equipped units tasked with executing critical offensive and defensive operations on behalf of a state or empire.
-
E.
Soviet field army
A Soviet field army was a large, operational-level military formation of the Soviet Armed Forces, typically comprising multiple corps or divisions, support units, and command structures, organized to conduct sustained offensive or defensive campaigns in a designated theater of operations.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:25 p.m.