Triple
T32994768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundesautobahn 57 |
E844194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Autobahn in Deutschland |
C44432
|
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: Autobahn in Deutschland Context triple: [Bundesautobahn 57, instanceOf, Autobahn in Deutschland]
-
A.
Autobahn in Germany
chosen
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.
-
B.
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.
-
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.
Autobahnkreuz
An Autobahnkreuz is a grade-separated, often multi-level highway interchange where two German autobahns intersect, enabling high-speed, non-stop traffic flow between all directions.
-
E.
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.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.