Triple
T7078903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombardment of Sveaborg |
E164892
|
entity |
| Predicate | coordinateAttackWith |
P64893
|
FINISHED |
| Object | Royal Navy Baltic Fleet operations |
—
|
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: Royal Navy Baltic Fleet operations | Statement: [Bombardment of Sveaborg, coordinateAttackWith, Royal Navy Baltic Fleet operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateAttackWith Context triple: [Bombardment of Sveaborg, coordinateAttackWith, Royal Navy Baltic Fleet operations]
-
A.
coordinatedAttacksAlsoTargeted
Indicates that in a set of coordinated attacks, the same target was also attacked as part of those coordinated actions.
-
B.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
C.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
D.
coordinateOperationWith
chosen
Indicates that one entity organizes and aligns its actions or processes with another entity to achieve a coordinated outcome.
-
E.
counterattackBy
Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
- 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.