Triple
T1090982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Shiloh |
E24161
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Civil War battle |
C647
|
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: American Civil War battle Context triple: [Battle of Shiloh, instanceOf, American Civil War battle]
-
A.
battles
chosen
Battles are organized, often large-scale armed conflicts between opposing forces, characterized by strategic maneuvers, tactical engagements, and the pursuit of specific military objectives within a defined time and place.
-
B.
American Civil War memory tradition
American Civil War memory tradition is the evolving set of narratives, commemorations, symbols, and cultural practices through which different groups in the United States have interpreted, justified, contested, and remembered the causes, events, and consequences of the Civil War over time.
-
C.
United States national battlefield
A United States national battlefield is a protected area designated by the federal government to preserve and interpret the site of a significant historic battle, typically from the American Civil War, for public education and commemoration.
-
D.
historic battlefield
A historic battlefield is a geographically defined site where significant military engagements occurred, preserved or recognized for its cultural, educational, and commemorative value.
-
E.
campaign of the Russian Civil War
A campaign of the Russian Civil War is a coordinated series of military operations conducted by opposing factions over a specific region and period, aimed at achieving strategic political and territorial objectives within the broader conflict.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:42 p.m.