Triple
T28137916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shevchenkivskyi District, Kyiv |
E714258
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative district of Kyiv |
C25224
|
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: administrative district of Kyiv Context triple: [Shevchenkivskyi District, Kyiv, instanceOf, administrative district of 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.
raion of Ukraine
chosen
A raion of Ukraine is an administrative district within an oblast that serves as a second-level territorial unit for local governance and administration.
-
C.
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.
-
D.
former raion of Ukraine
A former raion of Ukraine is an administrative district that existed as a second-level territorial unit within Ukraine’s regional structure but was later dissolved or reorganized, typically due to administrative reforms.
-
E.
district of Budapest
A district of Budapest is an administrative subdivision of Hungary’s capital city, each with its own local government, distinct neighborhoods, and specific urban, cultural, and historical characteristics.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 9:51 p.m.