Triple
T37667451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action of 23 November 1939 |
E937858
|
entity |
| Predicate | BritishShipFate |
P178865
|
FINISHED |
| Object | HMS Rawalpindi sunk |
—
|
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: HMS Rawalpindi sunk | Statement: [Action of 23 November 1939, BritishShipFate, HMS Rawalpindi sunk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BritishShipFate Context triple: [Action of 23 November 1939, BritishShipFate, HMS Rawalpindi sunk]
-
A.
britishShipsLost
chosen
Indicates that the subject refers to British ships that were lost, typically through sinking, capture, or destruction, in a particular event or context.
-
B.
EnglishShipsSunkOrCaptured
Indicates that English ships were either sunk or captured as a result of a particular event or action.
-
C.
BritishShipRate
Indicates that the subject is classified or rated according to the British naval ship rating system (e.g., first-rate, second-rate, etc.).
-
D.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
E.
BritishShipType
Indicates that the entity is classified as a type of ship associated with Britain, typically by origin, design, or service.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba9e27d0c81908342e28f016d221a |
completed | May 6, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.