Triple
T7078915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombardment of Sveaborg |
E164892
|
entity |
| Predicate | casualtiesDefender |
P1399
|
FINISHED |
| Object | several hundred killed and wounded |
—
|
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: several hundred killed and wounded | Statement: [Bombardment of Sveaborg, casualtiesDefender, several hundred killed and wounded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesDefender Context triple: [Bombardment of Sveaborg, casualtiesDefender, several hundred killed and wounded]
-
A.
casualties
chosen
Indicates that an event, action, or situation resulted in people being killed or injured.
-
B.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
C.
casualtiesDescription
Indicates a textual description of the human losses (such as deaths, injuries, or missing persons) resulting from an event or incident.
-
D.
casualtiesAttackersKilled
Indicates the number of attacking forces who were killed as a result of the attack.
-
E.
casualtiesInflictedOn
Indicates that one party has caused deaths or injuries to another party as a result of a harmful 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4ef47d48190b31125d1b57f7bec |
completed | March 27, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.