Triple
T34994222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Sonder |
E1009476
|
entity |
| Predicate | sunriseHikePopularity |
P20205
|
FINISHED |
| Object | popular sunrise hike destination |
—
|
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: popular sunrise hike destination | Statement: [Mount Sonder, sunriseHikePopularity, popular sunrise hike destination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sunriseHikePopularity Context triple: [Mount Sonder, sunriseHikePopularity, popular sunrise hike destination]
-
A.
isPopularDayHike
Indicates that a particular hiking route is widely favored and frequently chosen by people for day hikes.
-
B.
climbingPopularity
Indicates how widely practiced, favored, or in-demand a particular form of climbing or climbing-related activity is among participants.
-
C.
hasTouristPopularity
chosen
Indicates that a place or attraction is recognized as being popular or frequently visited by tourists.
-
D.
recommendedTimeToHike
Indicates the suggested or optimal time period during which one should undertake a particular hike.
-
E.
notableHike
Indicates that an entity is recognized as a significant or well-known hiking route or trail.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.