Triple
T18279025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizavetgrad |
E437814
|
entity |
| Predicate | renamedTo |
P3432
|
FINISHED |
| Object | Kirovo |
—
|
NE NERFINISHED |
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: Kirovo | Statement: [Elizavetgrad, renamedTo, Kirovo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kirovo Context triple: [Elizavetgrad, renamedTo, Kirovo]
-
A.
Kirovo
chosen
Kirovo was the Soviet-era name for the Ukrainian city now known as Kropyvnytskyi, reflecting its renaming in honor of Bolshevik leader Sergei Kirov.
-
B.
Kuvshinovo
Kuvshinovo is a small town in Tver Oblast, Russia, known primarily as a local industrial and administrative center.
-
C.
Makeyevka
Makeyevka is an industrial city in eastern Ukraine’s Donetsk Oblast, historically known for its coal mining and metallurgical industries.
-
D.
Konstantinovka
Konstantinovka is an archaeological site in Ukraine notable for remains associated with the Eneolithic Sredny Stog culture, an early horse-using steppe society.
-
E.
Kolpashevo
Kolpashevo is a town in western Siberia, Russia, situated on the Ob River and serving as an administrative and economic center in the region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50054d1dc8190b31d02f617256e9d |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 10:34 a.m.