Triple
T27780383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Gale Fishing Company |
E699318
|
entity |
| Predicate | fateOfNotableVessel |
P152819
|
FINISHED |
| Object | Andrea Gail lost with all hands in 1991 |
—
|
NE NERFINISHED |
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: Andrea Gail lost with all hands in 1991 | Statement: [Sea Gale Fishing Company, fateOfNotableVessel, Andrea Gail lost with all hands in 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateOfNotableVessel Context triple: [Sea Gale Fishing Company, fateOfNotableVessel, Andrea Gail lost with all hands in 1991]
-
A.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
B.
notableVictimShip
Indicates that a ship is recognized as a particularly significant or noteworthy victim in a specific incident or context.
-
C.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
D.
fateOfDesignatedShip
chosen
Indicates the outcome or final status that befalls a specifically designated ship.
-
E.
fateOfLeadShip
Indicates the ultimate outcome or destiny that befalls the primary or leading ship in a given context or event.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:09 p.m.