Triple
T5327100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairview Dome |
E123211
|
entity |
| Predicate | bestKnownRouteGrade |
P44457
|
FINISHED |
| Object | Regular Route 5.9 |
—
|
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: Regular Route 5.9 | Statement: [Fairview Dome, bestKnownRouteGrade, Regular Route 5.9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestKnownRouteGrade Context triple: [Fairview Dome, bestKnownRouteGrade, Regular Route 5.9]
-
A.
climbingGradeContext
Indicates the grading system or contextual scale used to express the difficulty rating of a climb.
-
B.
primaryClimbingDifficulty
chosen
Indicates the main level of challenge or technical difficulty associated with a climbing route or problem.
-
C.
hasTrailDifficulty
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
D.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
E.
standardClimbingRouteType
Indicates the classification of a climbing route according to a recognized grading or style system.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85926c388190a495835caf927624 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.