Triple
T33328613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longstreet's Corps |
E853337
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate army corps |
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 army corps Context triple: [Longstreet's Corps, instanceOf, Confederate army corps]
-
A.
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.
-
B.
Confederate Army military district
A Confederate Army military district was a geographically defined administrative and operational area established by the Confederate States during the American Civil War to organize, command, and coordinate military forces and defenses within its boundaries.
-
C.
Union Army
The Union Army was the land-based military force of the United States (the Union) during the American Civil War, responsible for fighting the Confederate States and preserving the nation.
-
D.
Union Army infantry division
A Union Army infantry division was a mid-level Civil War combat formation composed of multiple infantry brigades, supporting artillery, and staff, organized to conduct sustained offensive and defensive operations under a divisional commander.
-
E.
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.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:34 a.m.