Triple
T25431913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Ridge (Integral) |
E637279
|
entity |
| Predicate | climbingDisciplines |
P9785
|
FINISHED |
| Object | rock 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: rock climbing | Statement: [South Ridge (Integral), climbingDisciplines, rock climbing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingDisciplines Context triple: [South Ridge (Integral), climbingDisciplines, rock climbing]
-
A.
climbingDiscipline
chosen
Indicates the specific style or category of climbing practiced or associated with an entity (e.g., bouldering, sport, trad).
-
B.
climbingCategory
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or 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.
climbingClass
Indicates the difficulty or grade level assigned to a climbing route, problem, or activity.
-
E.
climbingUse
Indicates that an entity uses or employs another entity as equipment, support, or aid specifically for climbing activities.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6db636c8190880178c72ed6d38a |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:58 p.m.