Triple

T13797878
Position Surface form Disambiguated ID Type / Status
Subject Continental Cup ski jumping events E331561 entity
Predicate scoringComponents P89407 FINISHED
Object jump distance 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: jump distance | Statement: [Continental Cup ski jumping events, scoringComponents, jump distance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scoringComponents
Context triple: [Continental Cup ski jumping events, scoringComponents, jump distance]
  • A. scoring
    Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
  • B. scoringType
    Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
  • C. scoringRecord
    Indicates that there exists a record documenting a scoring event or outcome associated with the given entities.
  • D. scoringDetail chosen
    Indicates a detailed breakdown of how a score was derived, including specific components, criteria, or events contributing to the overall score.
  • E. scoringUnit
    Indicates that one entity functions as a unit or component responsible for scoring or assigning scores to 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_69d81c58feb08190a77bca8bf7d6d20f completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de025be1f08190aac525d72d7dc0c3 completed April 14, 2026, 9:01 a.m.
PD Predicate disambiguation batch_69dbc85fb600819098a2aab48169be96 completed April 12, 2026, 4:29 p.m.
Created at: April 9, 2026, 10:11 p.m.