Triple
T18020135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shipwreck Beach |
E431093
|
entity |
| Predicate | shipwreckType |
P129444
|
FINISHED |
| Object | freighter |
—
|
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: freighter | Statement: [Shipwreck Beach, shipwreckType, freighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipwreckType Context triple: [Shipwreck Beach, shipwreckType, freighter]
-
A.
shipwreck
Indicates that a vessel has been destroyed, stranded, or severely damaged, typically at sea or near a shoreline.
-
B.
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.
-
C.
shipwreckUse
Indicates that an entity makes use of, interacts with, or derives benefit from a shipwreck.
-
D.
shipwreckedOn
Indicates that an entity becomes stranded or marooned on a particular landmass or location as a result of a shipwreck.
-
E.
causeOfShipwreck
Indicates the factor, event, or condition that directly led to a shipwreck occurring.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c1c5f88190a059ce4f86f7ed36 |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:24 a.m.