Triple
T24198219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Ridge (Mount Hunter) |
E599892
|
entity |
| Predicate | hasTypicalClimbingType |
P9785
|
FINISHED |
| Object | mixed climbing |
—
|
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: mixed climbing | Statement: [West Ridge (Mount Hunter), hasTypicalClimbingType, mixed climbing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalClimbingType Context triple: [West Ridge (Mount Hunter), hasTypicalClimbingType, mixed climbing]
-
A.
typeOfClimb
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
-
B.
hasClimbingActivity
Indicates that an entity engages in or is associated with a climbing-related activity.
-
C.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
D.
climbingCategory
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
E.
climbingDiscipline
chosen
Indicates the specific style or category of climbing practiced or associated with an entity (e.g., bouldering, sport, trad).
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.