Triple
T18020179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smugglers Cove |
E431094
|
entity |
| Predicate | hasShipwreckType |
P10943
|
FINISHED |
| Object | freighter shipwreck |
—
|
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 shipwreck | Statement: [Smugglers Cove, hasShipwreckType, freighter shipwreck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShipwreckType Context triple: [Smugglers Cove, hasShipwreckType, freighter shipwreck]
-
A.
hasShipwrecks
Indicates that one entity contains, includes, or is associated with shipwrecks located within it or under its control.
-
B.
hasTypeOfWreck
chosen
Indicates that one entity is classified as a specific type or category of wreck (e.g., shipwreck, car wreck) associated with another entity.
-
C.
shipwreckUse
Indicates that an entity makes use of, interacts with, or derives benefit from a shipwreck.
-
D.
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.
-
E.
shipwreck
Indicates that a vessel has been destroyed, stranded, or severely damaged, typically at sea or near a shoreline.
- 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_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. |
Created at: April 10, 2026, 10:24 a.m.