Triple
T29712185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eteläesplanadi |
E751811
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Helsinki |
C20687
|
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 Helsinki Context triple: [Eteläesplanadi, instanceOf, road in Helsinki]
-
A.
road in Finland
chosen
A road in Finland is a designated transportation route, ranging from major highways to local streets, that supports vehicular and sometimes pedestrian traffic while adhering to Finnish infrastructure, safety, and environmental standards.
-
B.
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.
-
C.
road in Sweden
A road in Sweden is a public or private transportation route within Swedish territory, designed and maintained for vehicular and sometimes pedestrian traffic, and governed by national and local regulations and standards.
-
D.
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.
-
E.
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.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:31 p.m.