Triple
T33088733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convoy PQ 17 |
E846712
|
entity |
| Predicate | notableGermanShipThreat |
—
|
GENERATED |
| Object | Tirpitz |
—
|
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: notableGermanShipThreat Context triple: [Convoy PQ 17, notableGermanShipThreat, Tirpitz]
-
A.
GermanShipRole
Indicates that an entity serves in a specific role or capacity on or for a German ship.
-
B.
GermanShipFate
Indicates the ultimate outcome or disposition of a German ship, such as whether it was sunk, captured, scuttled, or otherwise ended its service.
-
C.
GermanShipUndamaged
Indicates that a German ship remains intact and has not sustained damage.
-
D.
AustroHungarianShipInvolved
Indicates that a ship belonging to or operated by the Austro-Hungarian Empire was involved in a specified event or interaction.
-
E.
GneisenauOperator
Indicates that an entity serves as the operator or controlling organization responsible for Gneisenau.
- F. None of above. chosen
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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:26 a.m.