Triple
T21315698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balakliia |
E525463
|
entity |
| Predicate | hasRoadConnectionTo |
P11435
|
FINISHED |
| Object | Kupiansk |
—
|
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: Kupiansk | Statement: [Balakliia, hasRoadConnectionTo, Kupiansk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kupiansk Context triple: [Balakliia, hasRoadConnectionTo, Kupiansk]
-
A.
Kupiansk
chosen
Kupiansk is a strategically important city in Ukraine’s Kharkiv Oblast, serving as a key railway and logistics hub near the front lines of the Russo-Ukrainian War.
-
B.
Artemivsk
Artemivsk is the former Soviet-era name of the Ukrainian city now known as Bakhmut, located in the Donetsk region of eastern Ukraine.
-
C.
Voznesensk
Voznesensk is a city in southern Ukraine known as an industrial and transport center situated on the Southern Bug River.
-
D.
Orikhiv
Orikhiv is a frontline town in Ukraine’s Zaporizhzhia region that has become strategically important in the Russo-Ukrainian war.
-
E.
Korsun-Shevchenkivskyi
Korsun-Shevchenkivskyi is a town in central Ukraine known as the site of a major World War II battle during the Korsun–Shevchenkivsky Offensive.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dcf2534819097abbb2e9559e791 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 16, 2026, 4:28 p.m.