Triple
T21344340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Campbeltown |
E526288
|
entity |
| Predicate | purposeOfModification |
P6009
|
FINISHED |
| Object | deception during St Nazaire Raid |
—
|
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: deception during St Nazaire Raid | Statement: [HMS Campbeltown, purposeOfModification, deception during St Nazaire Raid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfModification Context triple: [HMS Campbeltown, purposeOfModification, deception during St Nazaire Raid]
-
A.
purposeOfUpgrade
Indicates that an upgrade is carried out with a specific intended purpose, goal, or reason in mind.
-
B.
reasonForChange
chosen
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
C.
renovationPurpose
Indicates that an entity is being renovated with a specific intended goal, use, or outcome in mind.
-
D.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
E.
modification
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
- 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8a85274f481909e699b390bed9350 |
completed | April 22, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:44 p.m.