Triple
T12987803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ust-Izhora |
E321814
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | populated place in Russia |
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: populated place in Russia Context triple: [Ust-Izhora, instanceOf, populated place in Russia]
-
A.
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.
-
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.
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.
-
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.
economic region of Russia
An economic region of Russia is a territorial grouping of federal subjects organized for coordinated economic planning, development, and statistical analysis based on shared geographic, industrial, and infrastructural characteristics.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:41 p.m.