Triple
T30018199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B180 Reschen Straße |
E762654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austrian federal highway |
C40672
|
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: Austrian federal highway Context triple: [B180 Reschen Straße, instanceOf, Austrian federal highway]
-
A.
Autobahn in Austria
The "Autobahn in Austria" class represents high-speed, limited-access motorway segments within Austria’s national road network, including their physical attributes, legal regulations, and operational characteristics.
-
B.
road in Austria
chosen
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.
-
C.
federal highway in Germany
A federal highway in Germany is a major national road, designated with a "B" number, that connects cities and regions to support long-distance and high-capacity motor traffic under federal jurisdiction.
-
D.
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.
-
E.
Polish expressway
A Polish expressway is a high-capacity, limited-access road in Poland designed for fast regional and intercity traffic, typically featuring dual carriageways, grade-separated junctions, and controlled entry and exit points.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:46 p.m.