Triple

T26565585
Position Surface form Disambiguated ID Type / Status
Subject Nordic combined at the 2010 Winter Olympics E666371 entity
Predicate skiJumpHillType P161037 FINISHED
Object large hill 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: large hill | Statement: [Nordic combined at the 2010 Winter Olympics, skiJumpHillType, large hill]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: skiJumpHillType
Context triple: [Nordic combined at the 2010 Winter Olympics, skiJumpHillType, large hill]
  • A. skiJumpingVenue
    Indicates that one entity serves as the ski jumping venue or facility associated with another entity (such as an event, competition, or organization).
  • B. skiFlyingHillHillSize
    Indicates the size classification or measurement of a ski flying hill.
  • C. skiAreaType
    Indicates the specific type or classification of a ski area associated with an entity (e.g., resort, backcountry, terrain park).
  • D. typeOfSkiing
    Indicates that one entity is a specific style, category, or kind of skiing in relation to another.
  • E. skiFlyingHillKPoint
    Indicates the designated K-point (critical distance) of a ski flying hill, defining the reference point used to measure and evaluate ski jumps.
  • F. None of above. chosen

Provenance (4 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_69ee9cf7e94481909f0d556b36e43572 completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f6149de5408190803077b6ef97b8f7 completed May 2, 2026, 3:13 p.m.
PD Predicate disambiguation batch_69f60b8bb0d08190ab5a9a2a8847c6f4 completed May 2, 2026, 2:34 p.m.
PDg Predicate description generation batch_69f60f24ed608190bffe6c6084fc2f7a completed May 2, 2026, 2:50 p.m.
Created at: April 27, 2026, 1:55 a.m.