Triple
T37368691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dent d’Oche |
E927778
|
entity |
| Predicate | hasViaFerrataSections |
P195026
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dent d’Oche, hasViaFerrataSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViaFerrataSections Context triple: [Dent d’Oche, hasViaFerrataSections, yes]
-
A.
hasClimbingRoutesOn
Indicates that one entity possesses or features climbing routes located on another entity (such as a rock face, wall, or structure).
-
B.
hasNumberOfClimbingRoutes
Indicates the quantity of climbing routes that are associated with or available at a given entity.
-
C.
hasClimbingTrail
Indicates that a location or area includes or provides access to a designated climbing trail.
-
D.
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.
-
E.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: May 3, 2026, 4:16 p.m.