Triple
T32299158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kala Patthar |
E825186
|
entity |
| Predicate | startingPointForAscent |
P73321
|
FINISHED |
| Object | Gorak Shep |
—
|
NE NERFINISHED |
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: Gorak Shep | Statement: [Kala Patthar, startingPointForAscent, Gorak Shep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingPointForAscent Context triple: [Kala Patthar, startingPointForAscent, Gorak Shep]
-
A.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
-
B.
climbStart
Indicates the moment or event when an entity begins the action of climbing something.
-
C.
onTypicalAscentRouteTo
Indicates that one entity lies along the standard or commonly used ascent route leading to another entity, typically in a climbing or mountaineering context.
-
D.
hasPopularAscentRouteFrom
chosen
Indicates that there exists a commonly used or well-known route for ascending to a place or peak starting from the specified origin location.
-
E.
notableAscent
Indicates that an entity is recognized for a significant rise, climb, or upward journey, such as an important ascent of a mountain or similar elevation.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: May 1, 2026, 12:44 a.m.