Triple
T34994203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Sonder |
E1009476
|
entity |
| Predicate | hasSummitTrack |
P33907
|
FINISHED |
| Object | Mount Sonder summit walk |
—
|
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: Mount Sonder summit walk | Statement: [Mount Sonder, hasSummitTrack, Mount Sonder summit walk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitTrack Context triple: [Mount Sonder, hasSummitTrack, Mount Sonder summit walk]
-
A.
hasSummitTrail
chosen
Indicates that there exists a trail or route leading to the summit or highest point of a geographic feature.
-
B.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
C.
hasSummitFeature
Indicates that a summit (or peak) possesses a particular characteristic, attribute, or notable feature.
-
D.
hasSummitIn
Indicates that an entity (such as a mountain or organization) has its summit or peak located within a specified place or region.
-
E.
hasSummitMarker
Indicates that a location or peak is marked by an official summit marker or sign denoting its highest point.
- 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_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: May 3, 2026, 4:01 p.m.