Triple
T35127800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranrapalca |
E1014356
|
entity |
| Predicate | typicalClimbers |
P206844
|
FINISHED |
| Object | experienced climbers |
—
|
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: experienced climbers | Statement: [Ranrapalca, typicalClimbers, experienced climbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClimbers Context triple: [Ranrapalca, typicalClimbers, experienced climbers]
-
A.
typeOfClimber
Indicates the specific category or style of climbing that a climber practices or is associated with.
-
B.
coClimber
Indicates that two or more entities participate together in the same climbing activity or ascent.
-
C.
commonlyClimbedWith
Indicates that one entity is typically climbed together with another entity, as part of the same ascent or route.
-
D.
climbingCategory
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
E.
climbingCommunity
Indicates a relationship where individuals are connected through shared participation or involvement in rock climbing activities and culture.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.