Triple
T24354196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ессентуки |
E613877
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | населённый пункт России |
C15728
|
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: населённый пункт России Context triple: [Ессентуки, instanceOf, населённый пункт России]
-
A.
district of Russia
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.
inhabited locality of Russia
chosen
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.
-
C.
city in Russia
A city in Russia is an urban locality within the Russian Federation that serves as a center of population, administration, economy, and culture, typically possessing municipal governance and infrastructure.
-
D.
municipal formation in Russia
A municipal formation in Russia is a legally defined local self-government entity, such as an urban or rural settlement, municipal district, or urban okrug, with its own elected bodies and administrative responsibilities within a specific territory.
-
E.
federal subject of Russia
A federal subject of Russia is a top-level administrative and political division of the Russian Federation, such as an oblast, republic, krai, autonomous okrug, federal city, or autonomous oblast, each with its own degree of autonomy and representation in federal institutions.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 1:59 a.m.