Triple
T17658136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Besseggen ridge hike |
E440177
|
entity |
| Predicate | bestTimeOfYear |
P121257
|
FINISHED |
| Object | June to September |
—
|
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: June to September | Statement: [Besseggen ridge hike, bestTimeOfYear, June to September]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestTimeOfYear Context triple: [Besseggen ridge hike, bestTimeOfYear, June to September]
-
A.
bestTimeToExperience
Indicates the optimal or most favorable time period during which an entity should be experienced or enjoyed.
-
B.
bestHikingMonths
chosen
Indicates the months of the year during which hiking conditions are considered most favorable for a given place or trail.
-
C.
bestTimeOfDayToVisit
Indicates the time of day during which visiting something is considered most optimal or desirable.
-
D.
timeOfYearPresented
Indicates the specific time or season of the year during which something is presented or takes place.
-
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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea3b4cc81908eec7032cf221d49 |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:33 a.m.