Triple
T27726998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ko Haa |
E697326
|
entity |
| Predicate | diveSiteLevel |
P103608
|
FINISHED |
| Object | suitable for beginners and experienced divers |
—
|
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: suitable for beginners and experienced divers | Statement: [Ko Haa, diveSiteLevel, suitable for beginners and experienced divers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diveSiteLevel Context triple: [Ko Haa, diveSiteLevel, suitable for beginners and experienced divers]
-
A.
hasDiveDifficulty
chosen
Indicates that an action or event of diving is associated with a specified level of difficulty.
-
B.
isDivingSite
Indicates that a location serves as a site where diving activities (such as scuba or free diving) can take place.
-
C.
hasDiveSite
Indicates that one entity possesses, is associated with, or provides access to a particular dive site.
-
D.
hasDiveSiteFeature
Indicates that a dive site possesses or includes a particular feature or characteristic.
-
E.
isMajorDiveDestination
Indicates that a location is widely recognized as a primary or highly popular destination for scuba diving activities.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f636417d448190bf3f54faeadabadc |
completed | May 2, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:09 p.m.