Triple
T28534397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thulusdhoo |
E722122
|
entity |
| Predicate | surfingAttraction |
P22583
|
FINISHED |
| Object | nearby reef breaks suitable for surfers |
—
|
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: nearby reef breaks suitable for surfers | Statement: [Thulusdhoo, surfingAttraction, nearby reef breaks suitable for surfers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfingAttraction Context triple: [Thulusdhoo, surfingAttraction, nearby reef breaks suitable for surfers]
-
A.
surfing
Indicates engaging in the activity of riding waves on a surfboard or similar equipment, typically on the surface of a body of water.
-
B.
hasSurfBreak
chosen
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.
surfingDiscipline
Indicates the specific type or style of surfing practiced or associated with an entity.
-
E.
hasBestTimeForSurfing
Indicates that a particular time or period is considered optimal for surfing conditions at a given location.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fd847008190b2e0f3364ac3fedd |
completed | May 2, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:31 a.m.