Triple
T35099465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leninskiye Gory |
E1012968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | locality in 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: locality in Moscow Context triple: [Leninskiye Gory, instanceOf, locality in 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.
building in Moscow
A building in Moscow is a constructed structure within the city’s urban environment, serving residential, commercial, governmental, or cultural functions and reflecting the architectural styles and historical layers of Russia’s capital.
-
D.
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.
-
E.
locality
A locality is a geographically bounded area, such as a neighborhood, town, or district, characterized by its specific physical setting, social community, and administrative identity.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.