Triple
T21760578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Henry |
E537152
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate stronghold |
C11829
|
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 stronghold Context triple: [Fort Henry, instanceOf, Confederate stronghold]
-
A.
Civil War site
chosen
A Civil War site is a historically significant location where events related to the American Civil War occurred, such as battles, encampments, or military operations, and is preserved or recognized for its cultural and educational value.
-
B.
colonial stronghold
A colonial stronghold is a heavily fortified settlement or military outpost established by a colonizing power to secure control, protect resources, and project authority over a foreign territory.
-
C.
Confederate monument
A Confederate monument is a public structure or statue commemorating individuals, units, or causes associated with the Confederate States of America, often serving as a focal point of historical memory and contemporary controversy.
-
D.
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.
-
E.
American Civil War era site
An American Civil War era site is a historically significant location—such as a battlefield, fort, encampment, prison, or related structure—directly associated with military, political, or social events of the United States Civil War (1861–1865).
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:50 p.m.