Triple
T31378542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strastnaya Square |
E800378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former name of Pushkinskaya Square |
C49757
|
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: former name of Pushkinskaya Square Context triple: [Strastnaya Square, instanceOf, former name of Pushkinskaya Square]
-
A.
former name of public square
chosen
A former name of public square is a historical designation previously used to identify a specific public square before it was officially renamed.
-
B.
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.
-
C.
Moscow Monorail station
A Moscow Monorail station is a designated stop along the Moscow Monorail system where passengers can board, alight, and transfer between monorail trains and other modes of public transportation.
-
D.
Moscow Central Circle station
A Moscow Central Circle station is a passenger rail facility on Moscow's orbital urban rail line that provides platforms, services, and access for trains and commuters within the city's integrated transit network.
-
E.
Volgograd Metrotram station
A Volgograd Metrotram station is a transit facility on the Volgograd Metrotram system that serves as a stop for light rail vehicles, providing passenger access, boarding, and transfers within the city’s hybrid tram–metro network.
- 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:18 p.m.