Triple
T11697126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ama Dablam |
E278024
|
entity |
| Predicate | climbingGradeStandardRoute |
P45131
|
FINISHED |
| Object | alpine D |
—
|
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: alpine D | Statement: [Ama Dablam, climbingGradeStandardRoute, alpine D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingGradeStandardRoute Context triple: [Ama Dablam, climbingGradeStandardRoute, alpine D]
-
A.
climbingDifficultyStandardRoute
Indicates the level of difficulty associated with ascending via the standard or most commonly used route.
-
B.
standardClimbingRouteType
Indicates the classification of a climbing route according to a recognized grading or style system.
-
C.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
D.
climbingGradeContext
chosen
Indicates the grading system or contextual scale used to express the difficulty rating of a climb.
-
E.
primaryClimbingRouteFor
Indicates that one climbing route is the main or most commonly used route for ascending a particular climbing objective or feature.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47cef60819088b7cc3a3a711e4c |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.