Triple
T563303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Kimberley |
E13499
|
entity |
| Predicate | damaged |
P993
|
FINISHED |
| Object | by enemy action during Mediterranean operations |
—
|
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: by enemy action during Mediterranean operations | Statement: [HMS Kimberley, damaged, by enemy action during Mediterranean operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: damaged Context triple: [HMS Kimberley, damaged, by enemy action during Mediterranean operations]
-
A.
damagedIn
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
-
B.
damagedBy
chosen
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
-
C.
hasDam
Indicates that a watercourse, reservoir, or similar feature is impounded or controlled by a specific dam.
-
D.
demolished
Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
-
E.
damageYear
Indicates the year in which the damage to an entity occurred or was recorded.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a712bc48190ba298b3c76ab11cc |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494c044648190a98589ab18935216 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.