Triple
T24082394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Saltus Lubbock |
E596538
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate States Army 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 States Army officer Context triple: [Thomas Saltus Lubbock, instanceOf, Confederate States Army 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.
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.
-
C.
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.
-
D.
Confederate States senator
A Confederate States senator was a member of the upper chamber of the legislature of the Confederate States of America, representing one of the seceded states in its national government during the American Civil War.
-
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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 10:43 p.m.