Triple
T23401742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batu Bolong Beach |
E559521
|
entity |
| Predicate | hasBestTimeForSurfing |
P152123
|
FINISHED |
| Object | around high tide |
—
|
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: around high tide | Statement: [Batu Bolong Beach, hasBestTimeForSurfing, around high tide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBestTimeForSurfing Context triple: [Batu Bolong Beach, hasBestTimeForSurfing, around high tide]
-
A.
hasBestSeasonForSurfing
Indicates that there is a particular season or time of year during which surfing conditions are considered optimal for a given location.
-
B.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
C.
discoveredAsSurfSpotBy
Indicates that a location became recognized and used as a surf spot through the actions or discovery of a particular person or group.
-
D.
hasSurfQuality
Indicates that something possesses a particular level or characteristic of surf quality, such as wave suitability or conditions for surfing.
-
E.
hasSurfingBeaches
Indicates that a location possesses beaches suitable or designated for surfing activities.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4e09ccc81909869d2c5f6d68432 |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:37 p.m.