Triple
T32216390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E-road |
E822935
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | part of the International E-road network |
C38492
|
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: part of the International E-road network Context triple: [European route E-road, instanceOf, part of the International E-road network]
-
A.
trans-European road
chosen
A trans-European road is a major transportation route that crosses multiple European countries, facilitating international travel and trade across the continent.
-
B.
trans-European transport network route
A trans-European transport network route is a designated corridor within the EU-wide integrated transport system that connects key cities, ports, and regions across Europe to facilitate efficient, interoperable, and sustainable cross-border movement of people and goods.
-
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.
federal highway of Russia
A federal highway of Russia is a major national roadway that forms part of the country’s primary transport network, connecting key cities, regions, and borders under federal jurisdiction and maintenance.
-
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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:37 a.m.