Triple
T23749304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakey Peak |
E586913
|
entity |
| Predicate | hasBestSwellDirection |
P56826
|
FINISHED |
| Object | southwest swell |
—
|
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: southwest swell | Statement: [Lakey Peak, hasBestSwellDirection, southwest swell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBestSwellDirection Context triple: [Lakey Peak, hasBestSwellDirection, southwest swell]
-
A.
hasBestTimeForSurfing
Indicates that a particular time or period is considered optimal for surfing conditions at a given location.
-
B.
bestSwellDirection
chosen
Indicates the swell direction from which waves produce the most favorable or optimal surfing conditions at a given location.
-
C.
waveDirection
Indicates the direction in which a wave is propagating or traveling relative to a reference frame.
-
D.
hasBestSeasonForSurfing
Indicates that there is a particular season or time of year during which surfing conditions are considered optimal for a given location.
-
E.
hasBestSeasonForKiteboarding
Indicates the season or time of year during which conditions are most favorable for kiteboarding 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc118dc8190b0b92e402b9a7dd4 |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:13 p.m.