Triple
T23322509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William A. Fuller |
E591191
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate States of America military person |
C31519
|
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 of America military person Context triple: [William A. Fuller, instanceOf, Confederate States of America military person]
-
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 States of America person
chosen
A "Confederate States of America person" is an individual who was a citizen, resident, or active participant in the political, military, or civil life of the Confederate States of America during its existence from 1861 to 1865.
-
C.
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.
-
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.
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.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:07 p.m.