Triple
T23233649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schengen departures area |
E581228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | passenger processing area |
C10703
|
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: passenger processing area Context triple: [Schengen departures area, instanceOf, passenger processing area]
-
A.
passenger terminal area
A passenger terminal area is a designated zone within a transportation facility where travelers access services such as check-in, security, boarding, and baggage claim.
-
B.
passenger facility
A passenger facility is a designated area or building that provides services, amenities, and access points to support the boarding, alighting, and transit needs of travelers using a transportation system.
-
C.
passenger terminal concourse
chosen
A passenger terminal concourse is a large, central circulation space within a transport terminal where travelers move between entrances, ticketing, security, and boarding areas, often containing seating, retail, and information services.
-
D.
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.
-
E.
airport service area
An airport service area is the designated zone within and around an airport where operational, maintenance, and support activities are conducted to facilitate aircraft handling and passenger services.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
Created at: April 17, 2026, 4:09 p.m.