Triple
T3391435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Venture |
E71427
|
entity |
| Predicate | resultOfWreck |
P34334
|
FINISHED |
| Object | all passengers and crew reached Bermuda safely |
—
|
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: all passengers and crew reached Bermuda safely | Statement: [Sea Venture, resultOfWreck, all passengers and crew reached Bermuda safely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfWreck Context triple: [Sea Venture, resultOfWreck, all passengers and crew reached Bermuda safely]
-
A.
wreckSalvaged
Indicates that a previously wrecked object or structure has been recovered or salvaged from its damaged or sunken state.
-
B.
shipwreckUse
Indicates that an entity makes use of, interacts with, or derives benefit from a shipwreck.
-
C.
shipwreckEvent
Indicates an event in which a ship is destroyed, stranded, or severely damaged, typically resulting in loss or abandonment at sea or near a shoreline.
-
D.
wreckDiscovery
Indicates that an entity discovers, finds, or identifies a wreck (such as a ruined or destroyed object, vehicle, or structure).
-
E.
resultOfAccident
chosen
Indicates that something exists or occurs as a consequence or outcome of an accident.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb850594c81909b6f8a384fc98cb2 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.