Triple
T19100053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pointe Walker |
E467507
|
entity |
| Predicate | climbingAreaType |
P134369
|
FINISHED |
| Object | high alpine |
—
|
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: high alpine | Statement: [Pointe Walker, climbingAreaType, high alpine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingAreaType Context triple: [Pointe Walker, climbingAreaType, high alpine]
-
A.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
-
B.
climbingCategory
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
C.
climbingAreaStatus
Indicates the current condition or accessibility state of a climbing area (e.g., open, closed, restricted).
-
D.
climbedFeatureType
Indicates that an entity has climbed or ascended a particular type of physical feature (such as a mountain, wall, or similar structure).
-
E.
climbingRockType
Indicates that an entity is associated with or characterized by a particular type of rock used or encountered in climbing activities.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e36d279081908aeb472cd740c302 |
completed | April 20, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.