Triple
T18524643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brīvības bulvāris |
E452682
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Riga |
C40551
|
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: street in Riga Context triple: [Brīvības bulvāris, instanceOf, street in Riga]
-
A.
neighbourhood of Riga
A neighbourhood of Riga is a localized urban area within the city’s administrative boundaries, characterized by its own distinct residential, commercial, cultural, and social features.
-
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 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.
-
D.
road in Prague
A road in Prague is a public thoroughfare within the city’s urban fabric that supports vehicular and pedestrian movement while reflecting the historical layout, architectural context, and transportation infrastructure of the Czech capital.
-
E.
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.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:37 a.m.