Triple
T13710341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malyovitsa |
E328753
|
entity |
| Predicate | standardAscentDifficulty |
P4582
|
FINISHED |
| Object | non-technical hiking route in summer |
—
|
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 hiking route in summer | Statement: [Malyovitsa, standardAscentDifficulty, non-technical hiking route in summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardAscentDifficulty Context triple: [Malyovitsa, standardAscentDifficulty, non-technical hiking route in summer]
-
A.
climbingDifficultyStandardRoute
chosen
Indicates the level of difficulty associated with ascending via the standard or most commonly used route.
-
B.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
-
C.
typicalAscentStyle
Indicates the usual or characteristic manner or technique by which an ascent or climb is performed.
-
D.
difficultyClassRange
Indicates the range of difficulty classes within which an action, task, or challenge is considered to fall.
-
E.
typicalAscentCombinedWith
Indicates that one ascent or climbing route is normally undertaken together with another as part of a standard or customary combined itinerary.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd43949e6c8190ae5e4fa119cde33a |
completed | April 13, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.