Triple
T23749303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakey Peak |
E586913
|
entity |
| Predicate | hasPeakSurfSeason |
P85439
|
FINISHED |
| Object | April–October |
—
|
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: April–October | Statement: [Lakey Peak, hasPeakSurfSeason, April–October]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakSurfSeason Context triple: [Lakey Peak, hasPeakSurfSeason, April–October]
-
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.
hasPeakVisitationSeason
Indicates that an entity experiences its highest or most concentrated level of visitation during a specific season or time period.
-
C.
hasBestTimeForSurfing
Indicates that a particular time or period is considered optimal for surfing conditions at a given location.
-
D.
hasSurfEvent
Indicates that a surf-related event is associated with or occurs at a given entity.
-
E.
hasDivingSeason
Indicates that there is a specific time period during which diving activities are permitted, optimal, or typically occur for a given entity or 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.