Triple
T24346845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MV Wilhelm Gustloff |
E613663
|
entity |
| Predicate | sankOffCoastOf |
P86676
|
FINISHED |
| Object | Pomerania |
E20284
|
NE 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: Pomerania | Statement: [MV Wilhelm Gustloff, sankOffCoastOf, Pomerania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sankOffCoastOf Context triple: [MV Wilhelm Gustloff, sankOffCoastOf, Pomerania]
-
A.
sunkOff
chosen
Indicates that one entity was sunk at a location situated off (near but not directly at) another referenced place or feature.
-
B.
sankOn
Indicates that one entity moved downward and became submerged or lower in level relative to another entity or reference point.
-
C.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
D.
sankOnMaidenVoyage
Indicates that the subject vessel sank during its very first voyage.
-
E.
placeOfSinking
Indicates the location where an object or entity sank or was submerged.
- F. None of above.
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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932978b88190afc441a3d4805e5f |
completed | April 29, 2026, 11:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fe3454e888190afba21a0e4ae5c6c |
completed | May 22, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:58 a.m.