Triple
T27365772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Russell |
E690156
|
entity |
| Predicate | popularityAmongClimbers |
P70853
|
FINISHED |
| Object | low to moderate |
—
|
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: low to moderate | Statement: [Mount Russell, popularityAmongClimbers, low to moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularityAmongClimbers Context triple: [Mount Russell, popularityAmongClimbers, low to moderate]
-
A.
numberOfFirstAscents
Indicates the count of times an entity has been the first to successfully ascend or climb a particular route, peak, or feature.
-
B.
alsoClimbed
Indicates that one entity climbed something that another specified entity also climbed.
-
C.
consideredByClimbersAs
chosen
Indicates that climbers regard or evaluate something in a particular way (e.g., as difficult, classic, dangerous, or high-quality).
-
D.
attemptedFirstAscentOf
Indicates that an entity made an effort to be the first to successfully climb or reach the summit of a particular route, peak, or feature.
-
E.
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.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 12:17 p.m.