Triple
T15557070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skaha Lake |
E370895
|
entity |
| Predicate | popularActivitySeason |
P78489
|
FINISHED |
| Object | boating in summer |
—
|
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: boating in summer | Statement: [Skaha Lake, popularActivitySeason, boating in summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularActivitySeason Context triple: [Skaha Lake, popularActivitySeason, boating in summer]
-
A.
seasonalActivitiesAtTop
Indicates that certain activities occur or are available at the top of a location (such as a hill, building, or structure) only during specific seasons.
-
B.
popularSeason
Indicates that a particular season is widely liked, favored, or frequently chosen by many people.
-
C.
peakSeasonReason
Indicates that there is a specific cause or justification for why a given time period is considered the peak season for something.
-
D.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
-
E.
popularTimeToVisit
chosen
Indicates the time period during which a place is most frequently visited or experiences peak visitor activity.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a97dbfc8190a98cbbac5e71ba88 |
completed | April 16, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:09 a.m.