Triple
T26554365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kambachen |
E671761
|
entity |
| Predicate | trekDifficultyFromGhunsa |
P24163
|
FINISHED |
| Object | moderate to strenuous |
—
|
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: moderate to strenuous | Statement: [Kambachen, trekDifficultyFromGhunsa, moderate to strenuous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trekDifficultyFromGhunsa Context triple: [Kambachen, trekDifficultyFromGhunsa, moderate to strenuous]
-
A.
hasTrailDifficulty
chosen
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
B.
относитсяККатегорииСложностиВосхождений
Indicates that something is associated with a specific category of climbing difficulty.
-
C.
climbingDifficultyContext
Indicates the contextual conditions or factors (such as environment, route type, or situation) under which a climbing difficulty assessment applies.
-
D.
dayOfTrek
Indicates the specific day or stage within a multi-day trek on which an event, action, or condition occurs.
-
E.
trekDistanceFromLukla
Indicates the trekking distance required to reach a location starting from Lukla.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6146527d481908aae1bf455f32714 |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:49 a.m.