Triple
T11897007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Ninth Corps front |
E283060
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Union Army formation sector |
C19405
|
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 formation sector Context triple: [Union Ninth Corps front, instanceOf, Union Army formation sector]
-
A.
army formation
chosen
An army formation is an organized arrangement of military units and personnel on the battlefield or during maneuvers, designed to optimize command, movement, and combat effectiveness.
-
B.
Canadian Army formation
A Canadian Army formation is an organized, hierarchical grouping of military units (such as brigades or divisions) structured to conduct land operations under a unified command within the Canadian Armed Forces.
-
C.
Continental Army brigade formation
A Continental Army brigade formation was a tactical military unit composed of several regiments organized under a brigadier general, arranged on the battlefield to coordinate infantry, artillery, and support elements during the American Revolutionary War.
-
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.
United States Army formation type
A United States Army formation type is a standardized organizational structure that defines the size, composition, and command hierarchy of Army units for specific operational roles and missions.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.