Triple
T6831965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Fork Canyon |
E157157
|
entity |
| Predicate | recreationSeasonPeak |
P42818
|
FINISHED |
| Object | 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: summer | Statement: [American Fork Canyon, recreationSeasonPeak, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationSeasonPeak Context triple: [American Fork Canyon, recreationSeasonPeak, summer]
-
A.
recreationSeason
chosen
Indicates the time of year or specific season during which a recreational activity, facility, or area is typically used or available.
-
B.
climbingSeason
Indicates the period during which climbing an object, route, or area is typically allowed, feasible, or considered optimal.
-
C.
hasWinterSportsSeason
Indicates that an entity participates in, is associated with, or has a defined period for winter sports activities or competitions.
-
D.
popularSeason
Indicates that a particular season is widely liked, favored, or frequently chosen by many people.
-
E.
seasonalTourism
Indicates that tourism activity in a place varies significantly by season, with distinct peak and off-peak periods.
- 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62992908190996efab71cbf70f0 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.