Triple
T8623839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gagarinsky District, Smolensk Oblast |
E204235
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Smolensk Oblast |
C15426
|
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: district of Smolensk Oblast Context triple: [Gagarinsky District, Smolensk Oblast, instanceOf, district of Smolensk Oblast]
-
A.
district of Russia
chosen
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.
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.
district of Saxony
A district of Saxony is an administrative subdivision within the federal state of Saxony in Germany, responsible for local governance, public services, and regional planning across multiple municipalities.
-
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.
inhabited locality of Russia
An inhabited locality of Russia is a distinct, officially recognized populated place within the territory of the Russian Federation, such as a city, town, village, or settlement, where people reside permanently or temporarily.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.