Triple
T16977265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Hampton Roads |
E411845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ironclad engagement |
C21550
|
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: ironclad engagement Context triple: [Battle of Hampton Roads, instanceOf, ironclad engagement]
-
A.
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.
-
B.
Apache Wars engagement
An Apache Wars engagement is a specific military confrontation or skirmish between Apache groups and opposing forces (such as U.S. or Mexican military or settlers) during the broader series of conflicts known as the Apache Wars.
-
C.
civil war battle
chosen
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.
-
D.
cavalry charge
A cavalry charge is a rapid, coordinated forward attack by mounted troops intended to break enemy lines through speed, shock, and momentum.
-
E.
engagement of the Second English Civil War
The engagement of the Second English Civil War refers to the series of military confrontations and political maneuvers between Royalist forces and the Parliamentarian New Model Army in 1648, culminating in decisive battles such as Preston that led to the defeat of Charles I’s supporters and paved the way for his trial and execution.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:32 a.m.