Triple

T34549059
Position Surface form Disambiguated ID Type / Status
Subject Западный административный округ города Москвы E887011 entity
Predicate instanceOf P0 FINISHED
Object административный округ Москвы C11622 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: административный округ Москвы
Context triple: [Западный административный округ города Москвы, instanceOf, административный округ Москвы]
  • A. administrative okrug of Moscow chosen
    An administrative okrug of Moscow is a large territorial division of the city that groups several districts under a single local government for administrative and municipal management.
  • B. suburb of Moscow
    A suburb of Moscow is a residential or mixed-use area located on the outskirts of Russia’s capital, typically characterized by commuter links to the city, mid- to high-density housing, and supporting local infrastructure and services.
  • C. district of Russia
    A district of Russia is an administrative subdivision within a federal subject that manages local governance, public services, and regional implementation of national laws for its constituent settlements.
  • D. федеральный округ России
    Федеральный округ России — это укрупнённая административно-территориальная единица, объединяющая несколько субъектов Российской Федерации для обеспечения эффективного федерального управления и координации деятельности органов власти.
  • E. местность Москвы
    Местность Москвы — это локализованный городской район столицы, характеризующийся исторически сложившейся застройкой, планировкой, социально-культурной средой и административной принадлежностью.
  • 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_69f349cff89081908f91e0b064f4833e completed April 30, 2026, 12:23 p.m.
Created at: May 1, 2026, 2:02 a.m.