Triple
T33247978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | airside secure area of Washington Dulles International Airport |
E851155
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport secure area |
C60769
|
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: airport secure area Context triple: [airside secure area of Washington Dulles International Airport, instanceOf, airport secure area]
-
A.
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.
-
B.
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.
-
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 authority
An airport authority is an organization responsible for the ownership, management, operation, and regulation of an airport or group of airports, ensuring safe, efficient, and compliant aviation services and facilities.
-
E.
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.
- F. None of above. chosen
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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:31 a.m.