Triple
T17215965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central European transport network |
E417852
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trans-European transport system |
C4130
|
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: trans-European transport system Context triple: [Central European transport network, instanceOf, trans-European transport system]
-
A.
European transport agreement
A European transport agreement is a formal, often multilateral, accord between European states that harmonizes rules, standards, and procedures for cross-border transportation of goods and passengers to ensure safety, efficiency, and legal consistency.
-
B.
transport infrastructure network
chosen
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
C.
transalpine railway
A transalpine railway is a rail line that crosses or traverses the Alps, typically using tunnels, viaducts, and mountain passes to connect regions on either side of the mountain range.
-
D.
transport corridor
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
-
E.
public transport information system
A public transport information system is a software platform that collects, processes, and disseminates real-time and scheduled data about public transit services to passengers, operators, and other stakeholders.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:38 a.m.