Triple
T29595659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulkovo Highway |
E754287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Saint Petersburg |
C25386
|
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: road in Saint Petersburg Context triple: [Pulkovo Highway, instanceOf, road in Saint Petersburg]
-
A.
street in Saint Petersburg
chosen
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.
-
B.
road in Moscow
A road in Moscow is a transportation route within the city’s urban network that facilitates vehicular and pedestrian movement between various districts, landmarks, and infrastructure.
-
C.
street in Riga
A street in Riga is a public urban thoroughfare within Latvia’s capital city, typically lined with a mix of historic and modern buildings, and serving as a route for pedestrian and vehicular traffic as well as local commerce and social activity.
-
D.
bridge in Saint Petersburg
A bridge in Saint Petersburg is a structural crossing over the city's numerous rivers and canals, often featuring historic architecture, movable spans, and serving as both vital transport infrastructure and a prominent element of the urban landscape.
-
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.
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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:17 p.m.