Triple

T22778409
Position Surface form Disambiguated ID Type / Status
Subject Metalist Stadium E563766 entity
Predicate tenant P75 FINISHED
Object FC Metalist Kharkiv 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 Metalist Kharkiv | Statement: [Metalist Stadium, tenant, FC Metalist Kharkiv]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FC Metalist Kharkiv
Context triple: [Metalist Stadium, tenant, FC Metalist Kharkiv]
  • A. FC Metalist Kharkiv chosen
    FC Metalist Kharkiv is a Ukrainian professional football club based in Kharkiv that has traditionally competed in the country’s top leagues and European competitions.
  • B. Metalist 1925 Kharkiv
    Metalist 1925 Kharkiv is a Ukrainian professional football club from Kharkiv that emerged as a phoenix club after the financial collapse of the original FC Metalist Kharkiv.
  • C. Metalurh Donetsk
    Metalurh Donetsk was a Ukrainian professional football club based in Donetsk that competed in the country’s top division before its dissolution.
  • D. HC Dynamo Kharkiv
    HC Dynamo Kharkiv is a professional ice hockey club based in Kharkiv, Ukraine.
  • E. FC Dnipro Cherkasy
    FC Dnipro Cherkasy is a Ukrainian football club based in the city of Cherkasy that competes in the national league system.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e24554497c819080b996e071de27c2 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17b631c6881908a6687920923dcf4 completed April 29, 2026, 3:30 a.m.
Created at: April 17, 2026, 3:28 p.m.