Triple
T31905524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autobahnkreuz Köln-Ost |
E814539
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Autobahnkreuz |
C60241
|
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: Autobahnkreuz Context triple: [Autobahnkreuz Köln-Ost, instanceOf, Autobahnkreuz]
-
A.
Autobahnkreuz
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Stuttgart S-Bahn line
A Stuttgart S-Bahn line is a specific rapid transit route within the Stuttgart metropolitan rail network that connects designated suburban and urban stations according to a defined timetable and service pattern.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, midnight