Triple

T34178196
Position Surface form Disambiguated ID Type / Status
Subject FC Kairat Futsal E876733 entity
Predicate isStrongContenderIn P108207 FINISHED
Object European futsal 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: European futsal competitions | Statement: [FC Kairat Futsal, isStrongContenderIn, European futsal competitions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isStrongContenderIn
Context triple: [FC Kairat Futsal, isStrongContenderIn, European futsal competitions]
  • A. hasNotableContender
    Indicates that an entity has a significant rival, challenger, or competitor recognized as noteworthy in relation to it.
  • B. isPerennialChampionshipContender chosen
    Indicates that an entity (typically a team or competitor) consistently ranks among the top contenders for a championship over multiple seasons or years.
  • C. isCandidate
    Indicates that an entity is being considered or put forward for a particular position, role, or selection process.
  • D. isStrongerThan
    Indicates that one entity possesses greater physical power, force, or effectiveness than another entity.
  • E. strongestIn
    Indicates that one entity possesses the greatest strength or power within a specified group, context, or comparison set.
  • 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_69f349ae640c8190b9cd220b5368d8b6 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7100315948190bc23da7543715446 completed May 3, 2026, 9:06 a.m.
PD Predicate disambiguation batch_69f70f3c5bfc81908585f52e196dafe5 completed May 3, 2026, 9:02 a.m.
Created at: May 1, 2026, 1:54 a.m.