Triple

T25274122
Position Surface form Disambiguated ID Type / Status
Subject TS Galaxy F.C. E633648 entity
Predicate qualifiedForSeason P96367 FINISHED
Object 2019–20 CAF Confederation Cup NE NERFINISHED

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: 2019–20 CAF Confederation Cup | Statement: [TS Galaxy F.C., qualifiedForSeason, 2019–20 CAF Confederation Cup]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: qualifiedForSeason
Context triple: [TS Galaxy F.C., qualifiedForSeason, 2019–20 CAF Confederation Cup]
  • A. qualifyingFor
    Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
  • B. firstSeasonEligible
    Indicates that this is the earliest season in which an entity becomes eligible to participate in or receive something.
  • C. qualifiedForTournament chosen
    Indicates that an entity meets the necessary criteria or requirements to participate in a particular tournament.
  • D. hasSeasonalParticipationIn
    Indicates that an entity takes part in or is involved with another entity only during specific seasons or recurring seasonal periods.
  • E. controlsPlayerEligibility
    Indicates a relationship where one entity determines or regulates whether a player is allowed to participate.
  • 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_69e75a92f48881909974ff9c11150a2e completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f55e519978819087a1676564a74630 completed May 2, 2026, 2:15 a.m.
PD Predicate disambiguation batch_69f4a0edd10c81908a052ab864d57c54 completed May 1, 2026, 12:47 p.m.
Created at: April 21, 2026, 1:17 p.m.