Triple
T20033311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joshua Lawrence Chamberlain’s bayonet charge at Little Round Top |
E497193
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Civil War battle maneuver |
C27529
|
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: Civil War battle maneuver Context triple: [Joshua Lawrence Chamberlain’s bayonet charge at Little Round Top, instanceOf, Civil War battle maneuver]
-
A.
civil war battle
A civil war battle is an armed conflict between organized factions within the same country, typically involving large-scale military engagements over political, territorial, or ideological control.
-
B.
military campaign maneuver
chosen
A military campaign maneuver is a coordinated movement or series of actions by armed forces designed to gain tactical or strategic advantage over an adversary within a broader operation or theater of war.
-
C.
engagement of the Battle of Gettysburg
The engagement of the Battle of Gettysburg is a specific military confrontation within the larger Battle of Gettysburg, involving the coordinated movements, combat actions, and tactical decisions of opposing forces during a defined phase of the three-day conflict.
-
D.
overland campaign
An overland campaign is a sustained military or strategic operation conducted across land, involving the coordinated movement and engagement of forces over extended distances and time.
-
E.
battle course
A battle course is a structured training environment or program designed to simulate combat scenarios and develop participants’ tactical, physical, and strategic skills.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:36 p.m.