Triple
T38442035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell Island |
E906522
|
entity |
| Predicate | shipwrecksUsedFor |
P37789
|
FINISHED |
| Object | recreational diving |
—
|
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: recreational diving | Statement: [Bell Island, shipwrecksUsedFor, recreational diving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipwrecksUsedFor Context triple: [Bell Island, shipwrecksUsedFor, recreational diving]
-
A.
shipsUsedAs
Indicates that certain ships are employed or repurposed to serve in a specified role, function, or capacity.
-
B.
hasShipwrecks
Indicates that one entity contains, includes, or is associated with shipwrecks located within it or under its control.
-
C.
shipwrecksDestroyedIn
Indicates that one or more shipwrecks were destroyed within a specified location or during a particular event or time period.
-
D.
shipwreckUse
chosen
Indicates that an entity makes use of, interacts with, or derives benefit from a shipwreck.
-
E.
usedForShips
Indicates that something is designed, intended, or suitable to be used for ships or ship-related purposes.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.