Triple
T15732206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyarny |
E381371
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | closed administrative-territorial formation |
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: closed administrative-territorial formation Context triple: [Polyarny, instanceOf, closed administrative-territorial formation]
-
A.
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.
-
B.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
C.
autonomous oblast
An autonomous oblast is a type of administrative division within a country that possesses a degree of self-governance and cultural or political autonomy, typically established to recognize and accommodate a specific ethnic or regional group.
-
D.
territorial state
A territorial state is a political entity that exercises sovereign authority over a clearly defined geographic area and the population within its borders.
-
E.
semi-autonomous territory
A semi-autonomous territory is a region within a sovereign state that possesses limited self-governing powers and administrative independence while remaining ultimately subject to the authority and constitution of the central government.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:46 a.m.