Triple
T19524462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuillin Ridge Traverse |
E488483
|
entity |
| Predicate | difficultyGradeContext |
P40322
|
FINISHED |
| Object | UK mountaineering |
—
|
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: UK mountaineering | Statement: [Cuillin Ridge Traverse, difficultyGradeContext, UK mountaineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: difficultyGradeContext Context triple: [Cuillin Ridge Traverse, difficultyGradeContext, UK mountaineering]
-
A.
difficultyGradingContext
chosen
Indicates the contextual factors or conditions that influence how difficult it is to assign a grade or evaluation to something.
-
B.
difficulty
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
C.
difficultyClassRange
Indicates the range of difficulty classes within which an action, task, or challenge is considered to fall.
-
D.
hasDifficultyContext
Indicates that something’s difficulty is defined, interpreted, or constrained within a particular situational or contextual framework.
-
E.
difficultySource
Indicates that one entity is the cause, origin, or contributing factor to the difficulty or challenge experienced in relation to another entity or situation.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63639cfc08190894ac67f7d861a25 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.