Triple
T16977304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Hampton Roads |
E411845
|
entity |
| Predicate | casualtiesConfederateWounded |
P34511
|
FINISHED |
| Object | 17 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 17 | Statement: [Battle of Hampton Roads, casualtiesConfederateWounded, 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesConfederateWounded Context triple: [Battle of Hampton Roads, casualtiesConfederateWounded, 17]
-
A.
confederateCasualtiesAndLosses
chosen
Indicates the number or extent of casualties and material losses suffered by Confederate forces in a conflict or engagement.
-
B.
casualtiesWounded
Indicates that an event or situation resulted in people being injured but not killed.
-
C.
wasWoundedIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or conflict.
-
D.
UnionKilledAndWounded
Indicates that members of the Union side in a conflict caused deaths and injuries to others.
-
E.
casualtiesBritishWounded
Indicates the number of British individuals who were wounded as a result of a specific event or action.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69e3d184f2cc81908ac629c8f87696f8 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.