Triple
T22652743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kozmodemyansk |
E559136
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | populated place on the Volga River |
C25863
|
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: populated place on the Volga River Context triple: [Kozmodemyansk, instanceOf, populated place on the Volga River]
-
A.
city in Russia
chosen
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.
-
B.
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.
-
C.
suburb of Moscow
A suburb of Moscow is a residential or mixed-use area located on the outskirts of Russia’s capital, typically characterized by commuter links to the city, mid- to high-density housing, and supporting local infrastructure and services.
-
D.
federal city of Russia
A federal city of Russia is a major urban locality that functions as a separate federal subject, holding the same administrative status as a region or republic and typically serving as a key political, economic, or cultural center.
-
E.
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.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:06 p.m.