Triple
T35958822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmund Fitzgerald shipwreck |
E1039940
|
entity |
| Predicate | bellRecovered |
P184282
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Edmund Fitzgerald shipwreck, bellRecovered, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bellRecovered Context triple: [Edmund Fitzgerald shipwreck, bellRecovered, 1995]
-
A.
debrisRecovered
Indicates that debris resulting from an event or incident has been successfully located, collected, and retrieved.
-
B.
recoveredIn
Indicates that something lost, damaged, or impaired has been restored or regained within a particular context, process, or location.
-
C.
recovered
Indicates that an entity has returned to a previous, healthier, normal, or functional state after a period of loss, damage, illness, or impairment.
-
D.
recoveryBy
Indicates that one entity regains or restores something (such as health, function, or a resource) through the action, intervention, or influence of another entity.
-
E.
recoveredThrough
Indicates that something was regained, restored, or obtained again by means of a specified method, process, or intermediary.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7ac2210e481909279dade5328825c |
completed | May 3, 2026, 8:12 p.m. |
Created at: May 3, 2026, 4:07 p.m.