Triple

T3035206
Position Surface form Disambiguated ID Type / Status
Subject Goûter Hut E82991 entity
Predicate approachDifficulty P2406 FINISHED
Object alpine PD to PD+ 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: alpine PD to PD+ | Statement: [Goûter Hut, approachDifficulty, alpine PD to PD+]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: approachDifficulty
Context triple: [Goûter Hut, approachDifficulty, alpine PD to PD+]
  • A. difficulty chosen
    Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
  • B. difficultyRelativeTo
    Indicates that one entity’s level of difficulty is being compared to and expressed in relation to another entity’s level of difficulty.
  • C. difficultyRelativeToOtherRoutes
    Indicates how the difficulty level of one route compares relative to other routes.
  • D. isDifficultToAccessBecauseOf
    Indicates that something is hard to reach, obtain, or use due to a specified obstacle, condition, or circumstance.
  • E. mayBeChallengedBy
    Indicates that one entity is allowed or able to be opposed, questioned, or contested by 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_69ad8b2298908190a7cb4e9bdbf064d0 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9b2a40b48190bfa7cdbb0fbd87f8 completed March 8, 2026, 3:52 p.m.
PD Predicate disambiguation batch_69ad961e2a408190afb1759132701305 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 3:01 p.m.