Triple
T14666317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teatralny Proyezd |
E344384
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Moscow |
C35200
|
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 Moscow Context triple: [Teatralny Proyezd, instanceOf, road in Moscow]
-
A.
road in Berlin
A road in Berlin is a public thoroughfare within the city’s urban network that facilitates vehicular, bicycle, and pedestrian movement while integrating with Berlin’s historical layout, public transit, and zoning infrastructure.
-
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.
road in Shanghai
A road in Shanghai is a transportation corridor within the city’s dense urban fabric that supports mixed traffic—vehicles, buses, bicycles, and pedestrians—while integrating local infrastructure, commercial activity, and municipal regulations specific to Shanghai.
-
D.
road in Hanoi
A road in Hanoi is a public transportation corridor within the city’s dense urban fabric, accommodating mixed traffic flows of motorbikes, cars, buses, and pedestrians while connecting residential, commercial, and cultural areas.
-
E.
road in Brasília
A road in Brasília is a planned vehicular and pedestrian circulation route that follows the city’s modernist, superquadra-based urban design, organizing traffic flow and connecting residential, commercial, and civic sectors.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:27 a.m.