Triple
T29215022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Texas, New Mexico, and Arizona |
E740644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate States Army administrative command |
C24282
|
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 administrative command Context triple: [District of Texas, New Mexico, and Arizona, instanceOf, Confederate States Army administrative command]
-
A.
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.
-
B.
Union Army field army
A Union Army field army was a large, operational-level Civil War military formation composed of multiple corps and supporting units, organized to conduct sustained campaigns and major battles for the United States.
-
C.
Confederate States Army unit
chosen
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.
-
D.
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.
-
E.
United States Army command
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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 12:13 p.m.