Triple
T18678670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prisojnik |
E456669
|
entity |
| Predicate | climbingRoutesInclude |
P132265
|
FINISHED |
| Object | north face routes |
—
|
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: north face routes | Statement: [Prisojnik, climbingRoutesInclude, north face routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingRoutesInclude Context triple: [Prisojnik, climbingRoutesInclude, north face routes]
-
A.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
B.
includedClimber
Indicates that a climber is part of, or counted within, a specified group, set, or collection of climbers.
-
C.
isClimbingRouteFeatureOn
Indicates that a specific climbing route feature is located on or part of a particular climbing route.
-
D.
primaryClimbingRouteFor
Indicates that one climbing route is the main or most commonly used route for ascending a particular climbing objective or feature.
-
E.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b26cb408190a4e209c0d4ff31ba |
completed | April 19, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:48 a.m.