Triple
T16977301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Hampton Roads |
E411845
|
entity |
| Predicate | casualtiesUnionKilled |
P125463
|
FINISHED |
| Object | 261 |
—
|
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: 261 | Statement: [Battle of Hampton Roads, casualtiesUnionKilled, 261]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesUnionKilled Context triple: [Battle of Hampton Roads, casualtiesUnionKilled, 261]
-
A.
casualtiesUnion
Indicates a relationship where multiple casualty figures or reports are combined into a single aggregated total.
-
B.
casualtiesUKKilled
Indicates that the relationship specifies the number of people from the UK who were killed in the referenced event or incident.
-
C.
UnionCasualtiesKilledAndWounded
Indicates the number of Union forces who were either killed or wounded as a result of a specific military engagement or event.
-
D.
englishCasualtiesKilledAndWounded
Indicates the number of English individuals who were either killed or wounded as a result of a particular event or conflict.
-
E.
UnionKilledAndWounded
Indicates that members of the Union side in a conflict caused deaths and injuries to others.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:32 a.m.