Triple
T24346848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MV Wilhelm Gustloff |
E613663
|
entity |
| Predicate | commanderOfAttackingVessel |
P816
|
FINISHED |
| Object | Alexander Marinesko |
—
|
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: Alexander Marinesko | Statement: [MV Wilhelm Gustloff, commanderOfAttackingVessel, Alexander Marinesko]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderOfAttackingVessel Context triple: [MV Wilhelm Gustloff, commanderOfAttackingVessel, Alexander Marinesko]
-
A.
commanderOfAttackedShip
Indicates that one entity is the commanding officer of a ship that is the target of an attack.
-
B.
attackedByVessel
Indicates that an entity is the target of an attack carried out by a vessel (such as a ship or boat).
-
C.
commanderAttacker
chosen
Indicates that one entity serves as the commanding officer or leader of another entity that is acting as the attacker in a conflict or operation.
-
D.
shipOwnedOrCommanded
Indicates that an entity either owns a ship or serves as its commanding authority.
-
E.
navalCommand
Indicates a relationship where one entity holds authority to direct, control, or oversee naval forces or maritime military operations involving another entity.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932978b88190afc441a3d4805e5f |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:58 a.m.