Triple

T30204111
Position Surface form Disambiguated ID Type / Status
Subject Liberian Premier League E767862 entity
Predicate runnerUpMayQualifyFor P54057 FINISHED
Object 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: CAF Confederation Cup | Statement: [Liberian Premier League, runnerUpMayQualifyFor, CAF Confederation Cup]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: runnerUpMayQualifyFor
Context triple: [Liberian Premier League, runnerUpMayQualifyFor, CAF Confederation Cup]
  • A. runnerUpQualification chosen
    Indicates that an entity attains a qualifying position or status specifically by being a runner-up in a competition or selection process.
  • B. losersMayQualifyFor
    Indicates that entities who lose in a given context can still become eligible for a subsequent opportunity, stage, or benefit.
  • C. qualifyingFor
    Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
  • D. mayHoldQualification
    Indicates that an entity is permitted or able to possess a particular qualification, certification, or credential.
  • E. winnerQualifiedFor
    Indicates that the entity identified as the winner has earned or met the conditions required to qualify for a subsequent stage, event, or status.
  • 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_69f2247eb0848190b4032f302d39c0d9 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67fc7921081909b4c17550cb08845 completed May 2, 2026, 10:50 p.m.
PD Predicate disambiguation batch_69f6760216108190bbb708d53a6c2c25 completed May 2, 2026, 10:09 p.m.
Created at: April 29, 2026, 7:31 p.m.