Triple
T5475878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Rainbow |
E122951
|
entity |
| Predicate | fateOfCapturedShip |
P23911
|
FINISHED |
| Object | USS Hancock taken into Royal Navy service |
—
|
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: USS Hancock taken into Royal Navy service | Statement: [HMS Rainbow, fateOfCapturedShip, USS Hancock taken into Royal Navy service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateOfCapturedShip Context triple: [HMS Rainbow, fateOfCapturedShip, USS Hancock taken into Royal Navy service]
-
A.
capturedShip
chosen
Indicates that one party has taken control of another party's ship, typically by force or seizure.
-
B.
fateOfComponentShip
Indicates the outcome or final status that befalls a component of a ship within the described context or event.
-
C.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
D.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
E.
fleetDestroyedBy
Indicates that a fleet was destroyed as a direct result of actions taken by another specified entity.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd923465c88190ad9c1b75b268f7ca |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.