Triple
T24488446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Froggatt Edge |
E617577
|
entity |
| Predicate | climbingGradesRange |
P156495
|
FINISHED |
| Object | from easier routes to very hard testpieces |
—
|
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: from easier routes to very hard testpieces | Statement: [Froggatt Edge, climbingGradesRange, from easier routes to very hard testpieces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingGradesRange Context triple: [Froggatt Edge, climbingGradesRange, from easier routes to very hard testpieces]
-
A.
climbingClass
Indicates the difficulty or grade level assigned to a climbing route, problem, or activity.
-
B.
primaryClimbingDifficulty
Indicates the main level of challenge or technical difficulty associated with a climbing route or problem.
-
C.
climbingGradeContext
Indicates the grading system or contextual scale used to express the difficulty rating of a climb.
-
D.
climbingClassification
Indicates the difficulty rating or grade assigned to a climbing route or problem.
-
E.
typeOfClimb
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
- 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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a9d795288190916368e3cec1f666 |
completed | April 30, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:22 a.m.