Triple
T38167420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army of Western Louisiana |
E953185
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate States Army field formation |
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: Confederate States Army field formation Context triple: [Army of Western Louisiana, instanceOf, Confederate States Army field formation]
-
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.
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.
-
C.
military formation collection
A military formation collection is an organized set of multiple military units or formations grouped together for coordinated command, maneuver, and operational effectiveness.
-
D.
militia-style military formation
A militia-style military formation is an organized group of primarily non-professional, part-time fighters drawn from the civilian population, structured for local defense or irregular warfare under limited formal military hierarchy and training.
-
E.
military formation concept
A military formation concept is an abstract representation of how armed forces are organized, arranged, and maneuvered on the battlefield to achieve tactical or strategic 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.