Triple
T12744818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Ohio |
E304576
|
entity |
| Predicate | keptAfloatBy |
P10291
|
FINISHED |
| Object | Royal Navy destroyers lashed alongside |
—
|
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: Royal Navy destroyers lashed alongside | Statement: [SS Ohio, keptAfloatBy, Royal Navy destroyers lashed alongside]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keptAfloatBy Context triple: [SS Ohio, keptAfloatBy, Royal Navy destroyers lashed alongside]
-
A.
refloated
chosen
Indicates that something previously afloat but no longer buoyant has been returned to a floating condition, typically by refilling with air or restoring buoyancy.
-
B.
Waterline
Indicates the level or line on an object or surface that marks where water reaches or has reached.
-
C.
keptWith
Indicates that one entity is stored, maintained, or held together in association with another entity.
-
D.
keptIn
Indicates that one entity is stored, contained, or maintained inside another entity as its location or container.
-
E.
survivesShipwreck
Indicates that an entity continues to live or remain alive after experiencing a shipwreck.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.