Triple
T4602182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Dynamo Kyiv |
E100344
|
entity |
| Predicate | notableRival |
P893
|
FINISHED |
| Object | FC Dnipro |
E200096
|
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 Dnipro | Statement: [FC Dynamo Kyiv, notableRival, FC Dnipro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FC Dnipro Context triple: [FC Dynamo Kyiv, notableRival, FC Dnipro]
-
A.
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.
-
B.
SC Dnipro-1
chosen
SC Dnipro-1 is a Ukrainian professional football club based in Dnipro that competes in the country’s top league.
-
C.
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.
-
D.
BC Dnipro
BC Dnipro is a professional basketball club based in Dnipro, Ukraine, competing in the country’s top basketball league.
-
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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd597462c08190bcdb3efd880778b1 |
completed | March 20, 2026, 2:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be1024cfec819089bd3a23325c9c13 |
completed | March 21, 2026, 3:27 a.m. |
Created at: March 20, 2026, 1:11 p.m.