Triple
T86440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Oklahoma (BB-37) |
E1737
|
entity |
| Predicate | founderedLocation |
P3148
|
FINISHED |
| Object | Pacific Ocean en route to West Coast scrapyard |
—
|
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: Pacific Ocean en route to West Coast scrapyard | Statement: [USS Oklahoma (BB-37), founderedLocation, Pacific Ocean en route to West Coast scrapyard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderedLocation Context triple: [USS Oklahoma (BB-37), founderedLocation, Pacific Ocean en route to West Coast scrapyard]
-
A.
placeOfSinking
chosen
Indicates the location where an object or entity sank or was submerged.
-
B.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
C.
dateOfSinking
Indicates the specific calendar date on which an entity (typically a vessel or structure) sank.
-
D.
shipInvolved
Indicates that a ship participates in, is associated with, or plays a role in a specified event or situation.
-
E.
notableShip
Indicates that there is a notable or significant ship associated with the subject 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a250e401288190ba12322c9c5f07c9 |
completed | Feb. 28, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69a24eb59e808190811c20518f39b1cc |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.