Triple
T8463306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SC Dnipro-1 |
E200096
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | Dnipro-1 |
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: Dnipro-1 | Statement: [SC Dnipro-1, shortName, Dnipro-1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dnipro-1 Context triple: [SC Dnipro-1, shortName, Dnipro-1]
-
A.
SC Dnipro-1
chosen
SC Dnipro-1 is a Ukrainian professional football club based in Dnipro that competes in the country’s top league.
-
B.
BC Dnipro
BC Dnipro is a professional basketball club based in Dnipro, Ukraine, competing in the country’s top basketball league.
-
C.
Dnipro
Dnipro is one of Ukraine’s largest industrial and cultural centers, located on the Dnieper River in the central-eastern part of the country.
-
D.
MFC Mykolaiv
MFC Mykolaiv is a Ukrainian football club based in the city of Mykolaiv.
-
E.
Dniprodzerzhynsk
Dniprodzerzhynsk (now officially called Kamianske) is an industrial city in central Ukraine known for its heavy industry and metallurgical enterprises along the Dnieper River.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4a39bd48190b72be7e03cff323b |
completed | March 31, 2026, 3:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce39d5f50081908e273d5286a0d397 |
completed | April 2, 2026, 9:41 a.m. |
Created at: March 30, 2026, 6:10 p.m.