Triple
T35372441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zamoskvorechye District, Central Administrative Okrug, Moscow |
E1021810
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neighborhood of Moscow |
C38220
|
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: neighborhood of Moscow Context triple: [Zamoskvorechye District, Central Administrative Okrug, Moscow, instanceOf, neighborhood of Moscow]
-
A.
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.
-
B.
местность Москвы
chosen
Местность Москвы — это локализованный городской район столицы, характеризующийся исторически сложившейся застройкой, планировкой, социально-культурной средой и административной принадлежностью.
-
C.
administrative okrug of Moscow
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.
-
D.
district of Saint Petersburg
A district of Saint Petersburg is an administrative territorial unit within the city that serves as a local level of government and organization for municipal services, population, and infrastructure.
-
E.
city in Russia
A city in Russia is an urban locality within the Russian Federation that serves as a center of population, administration, economy, and culture, typically possessing municipal governance and infrastructure.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.