Triple
T5304837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EuroAirport Basel–Mulhouse–Freiburg |
E120073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tri-national airport |
C81
|
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: tri-national airport Context triple: [EuroAirport Basel–Mulhouse–Freiburg, instanceOf, tri-national airport]
-
A.
international airport
chosen
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.
-
B.
international terminal area
An international terminal area is a designated section of an airport where passengers check in, depart, arrive, and transit for international flights, including associated facilities such as customs, immigration, security, and boarding gates.
-
C.
domestic airport
A domestic airport is an aviation facility that handles flights operating solely within a single country's borders, providing passenger, baggage, and aircraft services for internal air travel.
-
D.
public airport
A public airport is a government- or publicly-owned aviation facility open for use by the general public, providing infrastructure and services for commercial, private, and cargo air transportation.
-
E.
international port
An international port is a major maritime facility equipped to handle the arrival, departure, and transfer of cargo and passengers between countries, integrating customs, logistics, and transportation infrastructure.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:53 p.m.