Triple
T2623002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Administrative Okrug |
E59050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative okrug of Moscow |
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: administrative okrug of Moscow Context triple: [Western Administrative Okrug, instanceOf, administrative okrug of Moscow]
-
A.
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.
-
B.
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.
-
C.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
-
D.
district of Beijing
A district of Beijing is an administrative subdivision of the Beijing municipality that governs a specific urban or suburban area, providing local government services and regulation.
-
E.
municipal arrondissement of Paris
A municipal arrondissement of Paris is an administrative subdivision of the city, each with its own town hall, mayor, and local council responsible for certain municipal services and local governance within its boundaries.
- F. None of above. chosen
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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:50 p.m.