Triple
T26162832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Wrightson |
E654157
|
entity |
| Predicate | hasBestHikingSeason |
P161542
|
FINISHED |
| Object | spring |
—
|
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: spring | Statement: [Mount Wrightson, hasBestHikingSeason, spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBestHikingSeason Context triple: [Mount Wrightson, hasBestHikingSeason, spring]
-
A.
bestHikingMonths
Indicates the months of the year during which hiking conditions are considered most favorable for a given place or trail.
-
B.
bestHikingMonthsNorthernHemisphere
Indicates the months in the Northern Hemisphere that are considered most suitable or optimal for hiking.
-
C.
bestSeasonForTrekking
chosen
Indicates that a particular season is the most suitable or optimal time for trekking in a given place or context.
-
D.
hasEasiestSeason
Indicates that one season is considered the least difficult or most favorable compared to other seasons for a given activity, condition, or context.
-
E.
climbingSeason
Indicates the period during which climbing an object, route, or area is typically allowed, feasible, or considered optimal.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 8:31 p.m.