Triple
T15480914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Rodney |
E376912
|
entity |
| Predicate | roleInBismarckAction |
P16542
|
FINISHED |
| Object | delivered heavy gunfire that crippled Bismarck |
—
|
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: delivered heavy gunfire that crippled Bismarck | Statement: [HMS Rodney, roleInBismarckAction, delivered heavy gunfire that crippled Bismarck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBismarckAction Context triple: [HMS Rodney, roleInBismarckAction, delivered heavy gunfire that crippled Bismarck]
-
A.
roleInOperationWeserübung
Indicates the specific role or function an entity held in the context of Operation Weserübung.
-
B.
PrussianCommander
Indicates that an individual holds the position or role of a commander within the Prussian military forces.
-
C.
PrussianStrength
Indicates a relationship where an entity possesses or exhibits the military, political, or institutional power characteristic of Prussia.
-
D.
worldWarIIRole
chosen
Indicates the specific role, position, or function an entity had in relation to World War II.
-
E.
monarchOfPrussiaDuringWar
Indicates the person who held the position of monarch of Prussia during a specified war.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f8cb4388190a3b4c92c3bb4ad4f |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:34 a.m.