Triple
T26913138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoveniersstraat |
E677442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Antwerp |
C37665
|
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 Antwerp Context triple: [Hoveniersstraat, instanceOf, road in Antwerp]
-
A.
road in Belgium
chosen
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.
-
B.
road in the Netherlands
A road in the Netherlands is a public transportation route designed for vehicles, cyclists, and often pedestrians, built and maintained according to Dutch infrastructure standards and traffic regulations.
-
C.
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.
-
D.
road in Luxembourg
A road in Luxembourg is a designated public or private route within the country’s territory used for vehicular and pedestrian travel, identified by national or local classifications and integrated into Luxembourg’s transport network.
-
E.
road in Warsaw
A road in Warsaw is a public thoroughfare within the city’s boundaries that facilitates vehicular, bicycle, and pedestrian movement while connecting various urban districts and infrastructure.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 6:03 a.m.