Triple

T7205844
Position Surface form Disambiguated ID Type / Status
Subject Sokol Kiev E148662 entity
Predicate successorLeagueParticipation P30650 FINISHED
Object Ukrainian hockey competitions 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: Ukrainian hockey competitions | Statement: [Sokol Kiev, successorLeagueParticipation, Ukrainian hockey competitions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successorLeagueParticipation
Context triple: [Sokol Kiev, successorLeagueParticipation, Ukrainian hockey competitions]
  • A. successorTeamLeague chosen
    Indicates that one sports league is the direct successor to another for a given team’s participation or affiliation.
  • B. successorLeagueStructure
    Indicates that one league structure directly follows and replaces another in an organizational or temporal sequence.
  • C. successorLeagueLevel
    Indicates that one league level directly follows another in a hierarchical sequence, representing the next higher or lower tier in the league structure.
  • D. notableSuccessorLeague
    Indicates that one league is recognized as a prominent or historically significant successor to another league.
  • E. laterLeagueName
    Indicates that an entity’s league name was changed to a different (later) league name at some point in time.
  • 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_69c687e8cf188190b5f3ecffd681f04e completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e94ef5cc81908c33adcedf5c5054 completed March 27, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69c6e757fed4819091b0a096e3befc3a completed March 27, 2026, 8:23 p.m.
Created at: March 27, 2026, 2:52 p.m.