Triple
T259973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS West Virginia (BB-48) |
E5518
|
entity |
| Predicate | strickenFromNavalRegister |
P10294
|
FINISHED |
| Object | 1 March 1959 |
—
|
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: 1 March 1959 | Statement: [USS West Virginia (BB-48), strickenFromNavalRegister, 1 March 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strickenFromNavalRegister Context triple: [USS West Virginia (BB-48), strickenFromNavalRegister, 1 March 1959]
-
A.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
B.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
C.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
D.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
E.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
- F. None of above. chosen
Provenance (4 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25f921c2881908821ca2c03815eae |
completed | Feb. 28, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69a25b6b3ea88190bbd858999e42efae |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25f9163f881909232f8aea502cf80 |
completed | Feb. 28, 2026, 3:22 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.