Triple
T12512687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirovsky District, Leningrad Oblast |
E299118
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Leningrad 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 Leningrad Oblast Context triple: [Kirovsky District, Leningrad Oblast, instanceOf, district of Leningrad Oblast]
-
A.
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.
-
B.
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.
-
C.
district of Kaliningrad
A district of Kaliningrad is an administrative subdivision within the city of Kaliningrad, Russia, responsible for local governance, public services, and community infrastructure in its designated urban area.
-
D.
district of East Prussia
A district of East Prussia was an administrative subdivision of the former German province of East Prussia, responsible for local governance, justice, and public services within its defined territorial boundaries.
-
E.
district of Belarus
A district of Belarus is an administrative subdivision within a Belarusian region (oblast), responsible for local governance, public services, and implementation of national policies in its territory.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:57 p.m.