Triple

T23598118
Position Surface form Disambiguated ID Type / Status
Subject Atlético de Madrid 2017–18 UEFA Europa League campaign E582673 entity
Predicate roundOf32Opponent P152869 FINISHED
Object FC København 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: FC København | Statement: [Atlético de Madrid 2017–18 UEFA Europa League campaign, roundOf32Opponent, FC København]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roundOf32Opponent
Context triple: [Atlético de Madrid 2017–18 UEFA Europa League campaign, roundOf32Opponent, FC København]
  • A. thirdRoundOpponent
    Indicates that one entity is the opponent faced by another entity in the third round of a competition or tournament.
  • B. thirdRoundReplayOpponent
    Indicates that one entity is the opponent faced by another entity in a replay match of the third round of a competition or tournament.
  • C. facedOpponent
    Indicates that one entity directly confronted or competed against another as an opponent in a contest, conflict, or challenge.
  • D. fourthRoundOpponent
    Indicates that one entity is the opponent faced by another entity in the fourth round of a competition or tournament.
  • E. battleOpponent
    Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
  • F. None of above. chosen

Provenance (4 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_69e248f9e0a08190814772847003b1ff completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b091992c819085f8aa6cb91cb76a completed April 29, 2026, 7:17 a.m.
PD Predicate disambiguation batch_69f118c96a0081908a8ac98ef7e7e60c completed April 28, 2026, 8:30 p.m.
PDg Predicate description generation batch_69f121cc494081908c987adfcde89b0e completed April 28, 2026, 9:08 p.m.
Created at: April 17, 2026, 6:43 p.m.