Triple

T20159911
Position Surface form Disambiguated ID Type / Status
Subject Golden Fox FIS Ski World Cup races E491674 entity
Predicate runStructure P88494 FINISHED
Object two-run format in slalom 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: two-run format in slalom | Statement: [Golden Fox FIS Ski World Cup races, runStructure, two-run format in slalom]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: runStructure
Context triple: [Golden Fox FIS Ski World Cup races, runStructure, two-run format in slalom]
  • A. rootStructure
    Indicates that one entity serves as the primary or foundational structural element upon which another entity is based or organized.
  • B. raceStructure chosen
    Indicates a structural or organizational relationship that defines how a race (such as a competition or contest) is arranged, configured, or composed.
  • C. plannedStructure
    Indicates that one entity is a structure that is intended or designed to be built or established in the future, rather than already existing.
  • D. branchStructure
    Indicates how the parts of a branching system are organized and connected relative to one another.
  • E. viaStructure
    Indicates that one entity is connected to or accessed through a particular structural element or medium.
  • 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_69da6266c6888190bc1a3ecf24814d34 completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e667e37c8c8190827839291027d9e2 completed April 20, 2026, 5:52 p.m.
PD Predicate disambiguation batch_69e55b0c11cc8190836d1eee5945f000 completed April 19, 2026, 10:45 p.m.
Created at: April 11, 2026, 11:34 p.m.