Triple
T13362914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Lenana |
E318862
|
entity |
| Predicate | typicalAscentTimeFromHighCamp |
P40570
|
FINISHED |
| Object | 2–4 hours |
—
|
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: 2–4 hours | Statement: [Point Lenana, typicalAscentTimeFromHighCamp, 2–4 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAscentTimeFromHighCamp Context triple: [Point Lenana, typicalAscentTimeFromHighCamp, 2–4 hours]
-
A.
durationTypicalAscent
chosen
Indicates the typical amount of time required to complete an ascent.
-
B.
approximateAscentTimeFromRefuge
Indicates the estimated amount of time required to ascend from a specified refuge to a target point or destination.
-
C.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
D.
typicalBaseCampAltitude_m
Indicates the usual altitude, in meters, at which a base camp for an activity or expedition is typically established.
-
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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da628affd081909f1790d333f0eef4 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.