Triple
T28750997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unification Council of Kyiv 2018 |
E731525
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Kyiv |
C5517
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: event in Kyiv Context triple: [Unification Council of Kyiv 2018, instanceOf, event in Kyiv]
-
A.
neighborhood of Kyiv
A neighborhood of Kyiv is a distinct urban area within the city characterized by its own residential, commercial, cultural, and infrastructural features that contribute to the local identity and daily life of its inhabitants.
-
B.
town in Ukraine
A town in Ukraine is an urban locality with its own local government, infrastructure, and community, typically smaller than a city and situated within the administrative divisions of the country.
-
C.
settlement in Ukraine
A settlement in Ukraine is a populated locality, such as a city, town, village, or rural community, officially recognized within the country’s administrative-territorial structure.
-
D.
event in the Russo-Ukrainian War
chosen
An event in the Russo-Ukrainian War is a specific, temporally and geographically bounded occurrence—such as a battle, diplomatic action, territorial change, or significant incident—that affects the course, perception, or outcomes of the conflict.
-
E.
event in Uzbekistan
An event in Uzbekistan is a scheduled occurrence such as a cultural, social, political, or economic gathering that takes place within the geographic boundaries of Uzbekistan and involves participants, activities, and a specific time and location.
- F. None of above.
Provenance (1 batch)
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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 6:07 a.m.