Triple
T19371228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvian national road P122 |
E484540
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Latvia |
C41999
|
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 Latvia Context triple: [Latvian national road P122, instanceOf, road in Latvia]
-
A.
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.
-
B.
road in Finland
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.
-
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.
road in Austria
A road in Austria is a designated transportation route within Austrian territory, constructed and maintained for vehicular and pedestrian travel, and governed by national and regional traffic regulations.
-
E.
road in Belgium
A road in Belgium is a public transportation route, ranging from local streets to major highways, that connects cities, towns, and regions within Belgium and to neighboring countries, following national and European traffic regulations.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:35 p.m.