Triple
T28859814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Reval (1790) |
E728826
|
entity |
| Predicate | SwedishObjective |
P165674
|
FINISHED |
| Object | defeat Russian squadron at Reval |
—
|
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: defeat Russian squadron at Reval | Statement: [Battle of Reval (1790), SwedishObjective, defeat Russian squadron at Reval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SwedishObjective Context triple: [Battle of Reval (1790), SwedishObjective, defeat Russian squadron at Reval]
-
A.
SwedishTacticalAdvantage
Indicates that Sweden holds a superior strategic or tactical position over another party in a given context or conflict.
-
B.
strengthSweden
Indicates the level or degree of strength associated with Sweden in a given context.
-
C.
capturedStandardsBySwedes
Indicates that one party seized or took possession of military standards or flags from Swedish forces.
-
D.
AustrianObjective
Indicates that an entity has an objective, goal, or purpose specifically associated with Austria or Austrian context.
-
E.
nameInSwedish
Indicates that an entity is known or referred to by a particular name when expressed in the Swedish language.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a15e4c48190bcba6a5e930e2a9e |
completed | May 2, 2026, 8:09 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:46 a.m.