Triple
T533848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morecambe Bay |
E12282
|
entity |
| Predicate | 2004 cockling disaster |
P16533
|
FINISHED |
| Object | 23 Chinese migrant workers drowned |
—
|
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: 23 Chinese migrant workers drowned | Statement: [Morecambe Bay, 2004 cockling disaster, 23 Chinese migrant workers drowned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2004 cockling disaster Context triple: [Morecambe Bay, 2004 cockling disaster, 23 Chinese migrant workers drowned]
-
A.
missionAccident
Indicates that an accident or unintended harmful event occurred during the course of a mission or operation.
-
B.
Columbia disaster
Indicates the relationship of being involved in, affected by, or causally connected to the Space Shuttle Columbia disaster event.
-
C.
yearOfSinking
Indicates the specific calendar year in 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.
shipwreckedOn
Indicates that an entity becomes stranded or marooned on a particular landmass or location as a result of a shipwreck.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b3e49081909810fa417b31306f |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49857e1148190aa782b82675cf0b5 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.