Triple
T13026612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lacanau |
E326322
|
entity |
| Predicate | hasSurfEvent |
P107525
|
FINISHED |
| Object | professional surfing competitions |
—
|
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: professional surfing competitions | Statement: [Lacanau, hasSurfEvent, professional surfing competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfEvent Context triple: [Lacanau, hasSurfEvent, professional surfing competitions]
-
A.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
B.
hasSurfSchool
Indicates that a location or entity hosts, operates, or contains a surf school.
-
C.
hasInshoreRaces
Indicates that an entity conducts or includes races that take place in inshore or nearshore waters.
-
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.
hasBeachUse
Indicates that an entity is used for, designated for, or associated with beach-related activities or purposes.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efc07488190a15f3e41ea2db45c |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e3df2288190a7f27d31d248bb7f |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:53 p.m.