Triple
T1403957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regular Northwest Face |
E31647
|
entity |
| Predicate | notableFreeAscentStyle |
P27617
|
FINISHED |
| Object | free climbing |
—
|
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: free climbing | Statement: [Regular Northwest Face, notableFreeAscentStyle, free climbing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFreeAscentStyle Context triple: [Regular Northwest Face, notableFreeAscentStyle, free climbing]
-
A.
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.
-
B.
firstAscentBy
Indicates the person or party that first successfully ascended or climbed a particular route, peak, or feature.
-
C.
firstAscent
Indicates that an entity represents the earliest known successful ascent or climb of a particular route, peak, or feature.
-
D.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
E.
firstFreeAscentOfTheNoseBy
Indicates that the subject is the climber or party who made the first free ascent of the route known as “The Nose.”
- F. None of above. chosen
Provenance (4 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3a0330c8190b22452d29c79fcf4 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c11067b48190bca6ef3ac1475c20 |
completed | March 1, 2026, 10:43 p.m. |
Created at: March 1, 2026, 7:59 p.m.