Triple
T2443106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Drøbak Sound |
E53323
|
entity |
| Predicate | objectiveOfAttackers |
P38518
|
FINISHED |
| Object | capture Oslo by sea |
—
|
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: capture Oslo by sea | Statement: [Battle of Drøbak Sound, objectiveOfAttackers, capture Oslo by sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveOfAttackers Context triple: [Battle of Drøbak Sound, objectiveOfAttackers, capture Oslo by sea]
-
A.
mainAttacker
Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against another entity.
-
B.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
C.
opponentObjective
Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
-
D.
attacks
Indicates that one entity initiates an aggressive or harmful action directed toward another entity.
-
E.
protectionObjective
Indicates that one entity has the goal or purpose of safeguarding, defending, or preserving another entity or its interests.
- 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
| PDg | Predicate description generation | batch_69abcabe646c8190855d13b5dff07b97 |
completed | March 7, 2026, 6:50 a.m. |
Created at: March 6, 2026, 9:43 p.m.