Triple
T30432315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Нарышкин бастион |
E774203
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | достопримечательность Санкт-Петербурга |
C56492
|
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.
museum in Saint Petersburg
A museum in Saint Petersburg is a cultural institution that collects, preserves, researches, and exhibits artworks, historical artifacts, or scientific objects within the city of Saint Petersburg for public education and enrichment.
-
B.
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.
-
C.
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.
-
D.
street in Saint Petersburg
A street in Saint Petersburg is a public urban thoroughfare within the city’s historical or modern districts, typically lined with buildings and infrastructure that reflect the architectural, cultural, and social character of Russia’s northern capital.
-
E.
местность Москвы
Местность Москвы — это локализованный городской район столицы, характеризующийся исторически сложившейся застройкой, планировкой, социально-культурной средой и административной принадлежностью.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:07 p.m.