Triple
T8517938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BC Dnipro |
E201621
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | BC Dnipro |
E201621
|
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: BC Dnipro | Statement: [BC Dnipro, hasAbbreviation, BC Dnipro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BC Dnipro Context triple: [BC Dnipro, hasAbbreviation, BC Dnipro]
-
A.
BC Dnipro
chosen
BC Dnipro is a professional basketball club based in Dnipro, Ukraine, competing in the country’s top basketball league.
-
B.
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.
-
C.
SC Dnipro-1
SC Dnipro-1 is a Ukrainian professional football club based in Dnipro that competes in the country’s top league.
-
D.
FC Metalist Kharkiv
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.
-
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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe626787c819087e72dd76b2d9310 |
completed | March 31, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce88ec84208190ab72c8411e6cc4c2 |
completed | April 2, 2026, 3:19 p.m. |
Created at: March 30, 2026, 6:15 p.m.