Triple
T9182212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC Dynamo Kharkiv |
E220358
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | Dynamo Kharkiv |
E220358
|
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: Dynamo Kharkiv | Statement: [HC Dynamo Kharkiv, shortName, Dynamo Kharkiv]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dynamo Kharkiv Context triple: [HC Dynamo Kharkiv, shortName, Dynamo Kharkiv]
-
A.
HC Dynamo Kharkiv
chosen
HC Dynamo Kharkiv is a professional ice hockey club based in Kharkiv, Ukraine.
-
B.
Dynamo Minsk
Dynamo Minsk is a professional sports club from Minsk, Belarus, best known for its football team competing in the country’s top league and European competitions.
-
C.
FC Dnipro Cherkasy
FC Dnipro Cherkasy is a Ukrainian football club based in the city of Cherkasy that competes in the national league system.
-
D.
FC Dynamo Kyiv
FC Dynamo Kyiv is a historically successful Ukrainian professional football club renowned for its domestic dominance and strong performances in European competitions.
-
E.
BC Dnipro
BC Dnipro is a professional basketball club based in Dnipro, Ukraine, competing in the country’s top basketball league.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc25379008190b8ca047efe3bb7bb |
completed | April 1, 2026, 6:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d05c0eeb0c8190a5a22c662726805c |
completed | April 4, 2026, 12:32 a.m. |
Created at: March 30, 2026, 7:23 p.m.