Triple
T20497759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eisbachwelle |
E502917
|
entity |
| Predicate | surfingSeason |
P85439
|
FINISHED |
| Object | year-round |
—
|
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: year-round | Statement: [Eisbachwelle, surfingSeason, year-round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfingSeason Context triple: [Eisbachwelle, surfingSeason, year-round]
-
A.
hasBestSeasonForSurfing
chosen
Indicates that there is a particular season or time of year during which surfing conditions are considered optimal for a given location.
-
B.
bestSeasonForWindsurfing
Indicates the season during which conditions are most favorable for windsurfing at a given location.
-
C.
navigationSeason
Indicates the time period or season during which navigation or travel along a route or waterway is possible or permitted.
-
D.
surfingDiscipline
Indicates the specific type or style of surfing practiced or associated with an entity.
-
E.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
- 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cbefe4c819098af5bfd4d92341d |
completed | April 20, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.