Triple

T8908065
Position Surface form Disambiguated ID Type / Status
Subject FC Metalist Kharkiv E212110 entity
Predicate rival P437 FINISHED
Object FC Dynamo Kyiv E100344 NE 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: FC Dynamo Kyiv | Statement: [FC Metalist Kharkiv, rival, FC Dynamo Kyiv]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FC Dynamo Kyiv
Context triple: [FC Metalist Kharkiv, rival, FC Dynamo Kyiv]
  • A. FC Dynamo Kyiv chosen
    FC Dynamo Kyiv is a historically successful Ukrainian professional football club renowned for its domestic dominance and strong performances in European competitions.
  • B. FC Shakhtar Donetsk
    FC Shakhtar Donetsk is a leading Ukrainian professional football club, renowned for its domestic league success and regular participation in European competitions.
  • C. FC Dnipro
    FC Dnipro is a Ukrainian professional football club from Dnipro known for its strong domestic performances and notable runs in European competitions, including reaching the 2014–15 UEFA Europa League final.
  • D. FC Dnipro Cherkasy
    FC Dnipro Cherkasy is a Ukrainian football club based in the city of Cherkasy that competes in the national league system.
  • E. HC Dynamo Kharkiv
    HC Dynamo Kharkiv is a professional ice hockey club based in Kharkiv, Ukraine.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca839255248190b43984294abd92ae completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc64c6a87c81909331a39619f913c0 completed April 1, 2026, 12:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfc930a38c8190b57127efc824e036 completed April 3, 2026, 2:05 p.m.
Created at: March 30, 2026, 6:55 p.m.