Triple
T33088733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convoy PQ 17 |
E846712
|
entity |
| Predicate | notableGermanShipThreat |
P206347
|
FINISHED |
| Object | Tirpitz |
E144915
|
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: Tirpitz | Statement: [Convoy PQ 17, notableGermanShipThreat, Tirpitz]
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 (5 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34f024d5fc81908bd7f0e15219db40 |
completed | June 19, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:26 a.m.