Triple
T35018473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sister Islands of the Cayman Islands |
E1010122
|
entity |
| Predicate | divingSite |
P120467
|
FINISHED |
| Object | Bloody Bay Wall |
—
|
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: Bloody Bay Wall | Statement: [Sister Islands of the Cayman Islands, divingSite, Bloody Bay Wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divingSite Context triple: [Sister Islands of the Cayman Islands, divingSite, Bloody Bay Wall]
-
A.
divingVenue
Indicates a location or facility where diving activities or events take place.
-
B.
hasDiveSite
Indicates that one entity possesses, is associated with, or provides access to a particular dive site.
-
C.
isDivingSite
chosen
Indicates that a location serves as a site where diving activities (such as scuba or free diving) can take place.
-
D.
hasDiveSiteFeature
Indicates that a dive site possesses or includes a particular feature or characteristic.
-
E.
divingAccess
Indicates that one entity has permission or ability to engage in diving activities at or within another entity (such as a location, facility, or body of water).
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.