Triple
T25361845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Sand Dunes Recreation Area |
E635988
|
entity |
| Predicate | seasonOfPeakVisitation |
P127382
|
FINISHED |
| Object | fall |
—
|
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: fall | Statement: [Imperial Sand Dunes Recreation Area, seasonOfPeakVisitation, fall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonOfPeakVisitation Context triple: [Imperial Sand Dunes Recreation Area, seasonOfPeakVisitation, fall]
-
A.
hasPeakVisitationSeason
chosen
Indicates that an entity experiences its highest or most concentrated level of visitation during a specific season or time period.
-
B.
peakSeasonMonth
Indicates the month or months during which something (such as demand, activity, or occurrence) reaches its highest or most intense level.
-
C.
summerPeak
Indicates that something reaches its highest level, intensity, or activity during the summer season.
-
D.
summerTouristSeason
Indicates the period during summer when a place experiences increased tourist activity or visitation.
-
E.
popularTimeToVisit
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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 1:36 p.m.