Triple
T28813355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 奥穂高岳 |
E727574
|
entity |
| Predicate | 登山の難易度 |
P123916
|
FINISHED |
| Object | 上級者向けルートを含む |
—
|
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: 上級者向けルートを含む | Statement: [奥穂高岳, 登山の難易度, 上級者向けルートを含む]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 登山の難易度 Context triple: [奥穂高岳, 登山の難易度, 上級者向けルートを含む]
-
A.
summitDifficulty
Indicates the level of challenge or effort required to reach the summit of something (typically a mountain or peak).
-
B.
climbingDifficultyContext
chosen
Indicates the contextual conditions or factors (such as environment, route type, or situation) under which a climbing difficulty assessment applies.
-
C.
typeOfClimb
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
-
D.
относитсяККатегорииСложностиВосхождений
Indicates that something is associated with a specific category of climbing difficulty.
-
E.
relativeDifficultyAmong8000ers
Indicates the comparative level of climbing difficulty between different 8000-meter peaks.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f163a88190b1dd222eaa0f93ea |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:31 a.m.