Triple
T38331370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Met Station Camp |
E1037830
|
entity |
| Predicate | onTypicalAscentRouteTo |
P190430
|
FINISHED |
| Object | Point Lenana |
—
|
NE NERFINISHED |
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: Point Lenana | Statement: [Met Station Camp, onTypicalAscentRouteTo, Point Lenana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onTypicalAscentRouteTo Context triple: [Met Station Camp, onTypicalAscentRouteTo, Point Lenana]
-
A.
typicalAscentRouteVia
Indicates the usual or most commonly used route taken to ascend or reach a particular destination, such as a summit or high point.
-
B.
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.
-
C.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
D.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
-
E.
attemptedAscentOf
Indicates an action where an entity makes an effort to climb or ascend another entity, regardless of whether the ascent is completed successfully.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc7a4d7f881908b43b960911b81e9 |
completed | May 7, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69fcc589720c819089c8f500fea3c86a |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fcc7a42f68819081d6ec8bb6b53438 |
completed | May 7, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:30 p.m.