Triple
T498042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basel–Mulhouse–Freiburg transport corridor |
E10338
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transnational transport hub |
C82
|
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: transnational transport hub Context triple: [Basel–Mulhouse–Freiburg transport corridor, instanceOf, transnational transport hub]
-
A.
transport hub
chosen
A transport hub is a central location where multiple modes or routes of transportation intersect, enabling the efficient transfer of passengers or goods between them.
-
B.
international airport
An international airport is a large, complex transportation hub that facilitates the arrival, departure, and transfer of passengers and cargo between countries through scheduled and chartered flights, customs, immigration, and related services.
-
C.
rapid transit station
A rapid transit station is a designated facility where passengers board, alight, and transfer between high-frequency urban rail or metro services, typically featuring platforms, ticketing areas, and access to surrounding streets or other transport modes.
-
D.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
-
E.
commuter rail station
A commuter rail station is a designated facility where passengers board and alight regional trains that connect suburbs or outlying areas with urban centers, typically offering platforms, ticketing, and basic passenger amenities.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.