Triple
T29632185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byelostok, Grodno Governorate, Russian Empire |
E755603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | provincial city of the Russian Empire |
C55990
|
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: provincial city of the Russian Empire Context triple: [Byelostok, Grodno Governorate, Russian Empire, instanceOf, provincial city of the Russian Empire]
-
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.
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.
-
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.
city of oblast significance
A city of oblast significance is an urban locality that functions as an independent administrative unit within an oblast, holding a status equal to that of a district and governing its own municipal affairs.
-
E.
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.
- F. None of above. chosen
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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
Created at: April 28, 2026, 6:41 p.m.