Triple
T37285467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinizas |
E925520
|
entity |
| Predicate | standardRouteDifficultyIllinizaNorte |
P4582
|
FINISHED |
| Object | non-technical scramble |
—
|
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: non-technical scramble | Statement: [Illinizas, standardRouteDifficultyIllinizaNorte, non-technical scramble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardRouteDifficultyIllinizaNorte Context triple: [Illinizas, standardRouteDifficultyIllinizaNorte, non-technical scramble]
-
A.
standardRouteGradingApprox
Indicates an approximate assessment of how a particular route’s difficulty or quality compares to a standard grading or rating system.
-
B.
northSouthRoutes
Indicates that there are routes or connections running in a generally north–south direction between the related entities.
-
C.
climbingDifficultyStandardRoute
chosen
Indicates the level of difficulty associated with ascending via the standard or most commonly used route.
-
D.
difficultyRelativeToOtherRoutes
Indicates how the difficulty level of one route compares relative to other routes.
-
E.
northernDirection
Indicates a spatial relationship where one entity is located to the north of another entity.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 3, 2026, 4:16 p.m.