Triple
T12244734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutschland-class battleship |
E291821
|
entity |
| Predicate | notableShipFate |
P3345
|
FINISHED |
| Object | SMS Pommern sunk at Battle of Jutland in 1916 |
—
|
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: SMS Pommern sunk at Battle of Jutland in 1916 | Statement: [Deutschland-class battleship, notableShipFate, SMS Pommern sunk at Battle of Jutland in 1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableShipFate Context triple: [Deutschland-class battleship, notableShipFate, SMS Pommern sunk at Battle of Jutland in 1916]
-
A.
notableShip
chosen
Indicates that there is a notable or significant ship associated with the subject entity.
-
B.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
C.
shipTypeSunk
Indicates that a particular type of ship has been sunk as a result of some event or action.
-
D.
dispositionOfShips
Indicates the arrangement, allocation, or positioning of ships relative to a plan, location, or situation.
-
E.
hasShipwrecks
Indicates that one entity contains, includes, or is associated with shipwrecks located within it or under its control.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.