Triple
T28731962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porter Alexander |
E730683
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate officer |
C449
|
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 officer Context triple: [Porter Alexander, instanceOf, Confederate officer]
-
A.
Confederate Army general
A Confederate Army general was a high-ranking military officer who commanded Confederate forces during the American Civil War, overseeing strategy, operations, and troops in support of the secessionist Southern states.
-
B.
Confederate agent
A Confederate agent is an individual who covertly gathered intelligence, conducted sabotage, or engaged in clandestine operations in support of the Confederate States during the American Civil War.
-
C.
Confederate States Secretary of War
The Confederate States Secretary of War was the chief executive officer responsible for overseeing the Confederate States' War Department, including military administration, logistics, and coordination of the armed forces during the American Civil War.
-
D.
Georgia militia leader
A Georgia militia leader is an individual who commands and organizes local military forces within the state of Georgia, typically for defense, security, or emergency response purposes.
-
E.
military officer
chosen
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:58 a.m.