Triple
T16898360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frendo Spur |
E424367
|
entity |
| Predicate | oftenClimbedAs |
P74334
|
FINISHED |
| Object | one-day push from Chamonix valley |
—
|
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: one-day push from Chamonix valley | Statement: [Frendo Spur, oftenClimbedAs, one-day push from Chamonix valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenClimbedAs Context triple: [Frendo Spur, oftenClimbedAs, one-day push from Chamonix valley]
-
A.
usuallyClimbedAs
chosen
Indicates that an object, route, or feature is most commonly or traditionally ascended in a particular style, manner, or configuration.
-
B.
notableClimbs
Indicates that the subject has completed or is associated with particularly significant or well-known climbing routes or ascents.
-
C.
consideredByClimbersAs
Indicates that climbers regard or evaluate something in a particular way (e.g., as difficult, classic, dangerous, or high-quality).
-
D.
highestPeakClimbed
Indicates the tallest mountain or peak that an entity has successfully climbed.
-
E.
climbsTo
Indicates that one entity moves upward, typically with effort or by climbing, until it reaches another entity or a higher position.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8d98c308190bcc0adc7797d1f40 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.