Triple
T29319452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Residenzstraße |
E743474
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Munich |
C54826
|
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 Munich Context triple: [Residenzstraße, instanceOf, road in Munich]
-
A.
road in Frankfurt am Main
A road in Frankfurt am Main is a public thoroughfare within the city’s urban and suburban areas that facilitates vehicular, bicycle, and pedestrian traffic while connecting residential, commercial, and industrial zones.
-
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.
Autobahn in Germany
The "Autobahn in Germany" class represents high-speed, limited-access roadways within Germany’s national motorway network, characterized by controlled entry, variable or absent speed limits on certain segments, and infrastructure designed for efficient long-distance vehicular travel.
-
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 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.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:22 p.m.