Triple
T24388755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Driesh |
E614823
|
entity |
| Predicate | typicalAscentRouteIncludes |
P65032
|
FINISHED |
| Object | Shank of Drumfollow |
—
|
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: Shank of Drumfollow | Statement: [Driesh, typicalAscentRouteIncludes, Shank of Drumfollow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAscentRouteIncludes Context triple: [Driesh, typicalAscentRouteIncludes, Shank of Drumfollow]
-
A.
typicalAscentRouteVia
chosen
Indicates the usual or most commonly used route taken to ascend or reach a particular destination, such as a summit or high point.
-
B.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
C.
hasPopularAscentRouteFrom
Indicates that there exists a commonly used or well-known route for ascending to a place or peak starting from the specified origin location.
-
D.
typicalAscentCombinedWith
Indicates that one ascent or climbing route is normally undertaken together with another as part of a standard or customary combined itinerary.
-
E.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
- 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29456cc548190bb92b750fd2d04af |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:04 a.m.