Triple
T32319219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tallinn disaster |
E825726
|
entity |
| Predicate | notableShipLost |
—
|
GENERATED |
| Object | Soviet destroyer Yakov Sverdlov |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableShipLost Context triple: [Tallinn disaster, notableShipLost, Soviet destroyer Yakov Sverdlov]
-
A.
shipSankIn
Indicates that a specific ship sank (was lost or submerged) in a particular location or body of water.
-
B.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
C.
notableVictimShip
chosen
Indicates that a ship is recognized as a particularly significant or noteworthy victim in a specific incident or context.
-
D.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
E.
sankOnMaidenVoyage
Indicates that the subject vessel sank during its very first voyage.
- F. None of above.
Provenance (1 batch)
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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:46 a.m.