Triple
T18933182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Allen Fuller |
E463167
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate States of America military personnel |
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 personnel Context triple: [William Allen Fuller, instanceOf, Confederate States of America military personnel]
-
A.
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.
-
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.
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.
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.
-
E.
military confederacy
A military confederacy is a loose alliance of semi-independent states or groups that coordinate their armed forces and defense policies for mutual security while retaining significant political autonomy.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:59 a.m.