Triple
T24575301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Ostfront |
E608086
|
entity |
| Predicate | opposingShip |
P24650
|
FINISHED |
| Object | British battleship HMS Duke of York |
—
|
NE NERFINISHED |
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: British battleship HMS Duke of York | Statement: [Operation Ostfront, opposingShip, British battleship HMS Duke of York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingShip Context triple: [Operation Ostfront, opposingShip, British battleship HMS Duke of York]
-
A.
opponentShipClass
Indicates that one entity is the ship class of an opposing or enemy vessel relative to another entity.
-
B.
opponentFleet
Indicates that one fleet is in an adversarial or opposing relationship to another fleet.
-
C.
engagedEnemyShips
Indicates that one or more entities have actively attacked, exchanged fire with, or otherwise entered into direct combat with enemy ships.
-
D.
navalOpposition
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
-
E.
primaryAntagonistShip
chosen
Indicates that one ship serves as the main opposing or enemy vessel in relation to another entity or context.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a928896c8190af385755b1418ba6 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.