Triple

T34544434
Position Surface form Disambiguated ID Type / Status
Subject Alpental E886884 entity
Predicate hasSkiableTerrainType P163436 FINISHED
Object inbounds terrain 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: inbounds terrain | Statement: [Alpental, hasSkiableTerrainType, inbounds terrain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSkiableTerrainType
Context triple: [Alpental, hasSkiableTerrainType, inbounds terrain]
  • A. hasSkiableArea
    Indicates that an entity possesses an area of terrain that can be used for skiing.
  • B. hasOffPisteTerrain
    Indicates that a location or ski area includes terrain that is off the groomed or marked pistes, typically ungroomed or backcountry skiable areas.
  • C. skiTerrainType chosen
    Indicates the type of terrain or surface on which the skiing activity takes place.
  • D. hasSkiRunsFor
    Indicates that something provides or includes ski runs that are suitable or intended for a particular user group or purpose.
  • E. hasSkiAreaLevel
    Indicates that an entity is associated with a ski area of a particular level or difficulty classification.
  • 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_69f349ce5eb881909e431c670944aa68 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7201e241c819092d56a7bb99dc94d completed May 3, 2026, 10:14 a.m.
PD Predicate disambiguation batch_69f71cc8074c81909ae09bea2acf1a09 completed May 3, 2026, 10 a.m.
Created at: May 1, 2026, 2:02 a.m.