Triple
T33088725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convoy PQ 17 |
E846712
|
entity |
| Predicate | reasonForScattering |
P19352
|
FINISHED |
| Object | threat of attack by German surface fleet including battleship Tirpitz |
—
|
LITERAL 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: threat of attack by German surface fleet including battleship Tirpitz | Statement: [Convoy PQ 17, reasonForScattering, threat of attack by German surface fleet including battleship Tirpitz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForScattering Context triple: [Convoy PQ 17, reasonForScattering, threat of attack by German surface fleet including battleship Tirpitz]
-
A.
reasonForSplit
chosen
Indicates the cause, motivation, or circumstance that led to a separation or breakup between entities.
-
B.
scrappingReason
Indicates the reason or justification for discarding or scrapping an item, asset, or entity from use.
-
C.
reasonForFolding
Indicates the cause or justification for an entity being folded, discontinued, or terminated.
-
D.
reasonForRelocationOrFolding
Indicates the cause, motivation, or circumstance that led an entity (such as an organization, team, or operation) to move location or cease functioning entirely.
-
E.
reasonForDeployment
Indicates the underlying cause, purpose, or justification for which an entity is deployed or put into operation.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 1:26 a.m.