Triple
T16977303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Hampton Roads |
E411845
|
entity |
| Predicate | casualtiesConfederateKilled |
P34511
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Battle of Hampton Roads, casualtiesConfederateKilled, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesConfederateKilled Context triple: [Battle of Hampton Roads, casualtiesConfederateKilled, 7]
-
A.
confederateCasualtiesAndLosses
chosen
Indicates the number or extent of casualties and material losses suffered by Confederate forces in a conflict or engagement.
-
B.
casualtiesTexianKilled
Indicates that the relationship specifies the number of Texian individuals who were killed as casualties in a particular event or conflict.
-
C.
casualtiesProSlaveryKilled
Indicates that the casualties referenced were individuals who supported slavery and were killed.
-
D.
casualtiesKilledAndMortallyWounded
Indicates that the relationship records the number of individuals who were killed outright or died later from mortal wounds.
-
E.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
- 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.