Triple
T7164969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emmons–Winthrop route |
E167042
|
entity |
| Predicate | climbType |
P9785
|
FINISHED |
| Object | glacier route |
—
|
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: glacier route | Statement: [Emmons–Winthrop route, climbType, glacier route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbType Context triple: [Emmons–Winthrop route, climbType, glacier route]
-
A.
climbingCategory
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
B.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
C.
climbedFeatureType
Indicates that an entity has climbed or ascended a particular type of physical feature (such as a mountain, wall, or similar structure).
-
D.
climbingDiscipline
chosen
Indicates the specific style or category of climbing practiced or associated with an entity (e.g., bouldering, sport, trad).
-
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.
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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e832d2548190aacff0de80dbc268 |
completed | March 27, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.