Triple
T28859815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Reval (1790) |
E728826
|
entity |
| Predicate | SwedishOutcome |
P140014
|
FINISHED |
| Object | failed to destroy Russian squadron |
—
|
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: failed to destroy Russian squadron | Statement: [Battle of Reval (1790), SwedishOutcome, failed to destroy Russian squadron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SwedishOutcome Context triple: [Battle of Reval (1790), SwedishOutcome, failed to destroy Russian squadron]
-
A.
outcomeForSweden
chosen
Indicates the resulting effect, consequence, or result that a situation, event, or action has specifically in relation to Sweden.
-
B.
SwedishObjective
Indicates that an entity serves as the object or target of an action or relation specifically within a Swedish linguistic, cultural, or contextual framework.
-
C.
effectOnSweden
Indicates the impact or consequences that something has on Sweden.
-
D.
strengthSweden
Indicates the level or degree of strength associated with Sweden in a given context.
-
E.
statusInSweden
Indicates the legal, social, or official standing or condition that an entity holds within the context of Sweden.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:46 a.m.