Triple
T12824124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concourse C1 |
E306604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | passenger boarding 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 boarding area Context triple: [Concourse C1, instanceOf, passenger boarding 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 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.
-
C.
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.
-
D.
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.
-
E.
airport lounge
An airport lounge is a designated, often exclusive area within an airport that offers travelers a comfortable place to relax, work, and access amenities such as seating, refreshments, Wi‑Fi, and sometimes showers or business services while waiting for their flights.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:32 p.m.