Triple
T2627036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushkin, Saint Petersburg |
E59142
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division of Saint Petersburg |
C740
|
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 division of Saint Petersburg Context triple: [Pushkin, Saint Petersburg, instanceOf, administrative division of Saint Petersburg]
-
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.
regional division
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
C.
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.
-
D.
overseas territory subdivision
An overseas territory subdivision is an administrative division of a country located outside its mainland, typically subject to the sovereign state's authority while often possessing distinct legal, political, or cultural arrangements.
-
E.
administrative territorial entity
chosen
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:50 p.m.