Triple
T8908056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Metalist Kharkiv |
E212110
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | Metalist Kharkiv |
E212110
|
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: Metalist Kharkiv | Statement: [FC Metalist Kharkiv, shortName, Metalist Kharkiv]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Metalist Kharkiv Context triple: [FC Metalist Kharkiv, shortName, Metalist Kharkiv]
-
A.
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.
-
B.
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.
-
C.
HC Dynamo Kharkiv
HC Dynamo Kharkiv is a professional ice hockey club based in Kharkiv, Ukraine.
-
D.
Sokol Kiev
Sokol Kiev was an ice hockey club from Kyiv that competed at the top level of Soviet hockey in the Soviet Championship League.
-
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 (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_69cfba31fc148190a8dbe378694dcc32 |
completed | April 3, 2026, 1:01 p.m. |
Created at: March 30, 2026, 6:55 p.m.