Triple
T2148018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulhacén |
E47112
|
entity |
| Predicate | hasEasiestRouteGrade |
P4582
|
FINISHED |
| Object | non-technical walk in summer |
—
|
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: non-technical walk in summer | Statement: [Mulhacén, hasEasiestRouteGrade, non-technical walk in summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEasiestRouteGrade Context triple: [Mulhacén, hasEasiestRouteGrade, non-technical walk in summer]
-
A.
hasTrailDifficulty
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
B.
hasEasiestRoute
Indicates that one entity provides or represents the simplest or least difficult route or path to reach another entity or destination.
-
C.
climbingDifficultyStandardRoute
chosen
Indicates the level of difficulty associated with ascending via the standard or most commonly used route.
-
D.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
E.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeaa14bc81908486683decd7ae42 |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9846e88190b6c2941dd9ce7749 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.