Triple
T17333109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingiseppsky District |
E420863
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal district of Russia |
C22216
|
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: municipal district of Russia Context triple: [Kingiseppsky District, instanceOf, municipal district of Russia]
-
A.
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.
-
B.
municipal formation in Russia
chosen
A municipal formation in Russia is a legally defined local self-government entity, such as an urban or rural settlement, municipal district, or urban okrug, with its own elected bodies and administrative responsibilities within a specific territory.
-
C.
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.
-
D.
autonomous okrug of Russia
An autonomous okrug of Russia is a type of federal subject with a degree of self-governance, typically established in areas with significant indigenous or ethnic minority populations and often administratively associated with a larger region or krai.
-
E.
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.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:43 a.m.