Triple
T1403976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regular Northwest Face |
E31647
|
entity |
| Predicate | typicalAscentTime |
P6833
|
FINISHED |
| Object | 1 to 3 days for most parties |
—
|
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: 1 to 3 days for most parties | Statement: [Regular Northwest Face, typicalAscentTime, 1 to 3 days for most parties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAscentTime Context triple: [Regular Northwest Face, typicalAscentTime, 1 to 3 days for most parties]
-
A.
approximateAscentTimeFromRefuge
Indicates the estimated amount of time required to ascend from a specified refuge to a target point or destination.
-
B.
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.
-
C.
reachesSummit
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
-
D.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
E.
typicalTimes
chosen
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
- 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_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. |
Created at: March 1, 2026, 7:59 p.m.