Triple
T27507237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sotavento Beach |
E694309
|
entity |
| Predicate | hasBestSeasonForKitesurfing |
P104564
|
FINISHED |
| Object | summer months |
—
|
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: summer months | Statement: [Sotavento Beach, hasBestSeasonForKitesurfing, summer months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBestSeasonForKitesurfing Context triple: [Sotavento Beach, hasBestSeasonForKitesurfing, summer months]
-
A.
hasBestSeasonForKiteboarding
chosen
Indicates the season or time of year during which conditions are most favorable for kiteboarding at a given location.
-
B.
hasBestSeasonForSurfing
Indicates that there is a particular season or time of year during which surfing conditions are considered optimal for a given location.
-
C.
bestSeasonForWindsurfing
Indicates the season during which conditions are most favorable for windsurfing at a given location.
-
D.
hasBestTimeForSurfing
Indicates that a particular time or period is considered optimal for surfing conditions at a given location.
-
E.
bestSeasonForWindSports
Indicates the season during which conditions are most favorable for engaging in wind-based sports 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 1:14 p.m.