Triple
T34650033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 2 departure concourse |
E889809
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airside zone |
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: airside zone Context triple: [Terminal 2 departure concourse, instanceOf, airside zone]
-
A.
airport secure area
chosen
An airport secure area is a restricted zone beyond security checkpoints where only screened passengers, authorized personnel, and controlled goods are allowed, to ensure safety and regulatory compliance.
-
B.
airfield
An airfield is a designated area of land equipped with runways, taxiways, and minimal support facilities for the takeoff, landing, and ground movement of aircraft.
-
C.
airport runway
An airport runway is a long, specially prepared strip of land or pavement where aircraft take off and land, designed with specific markings, lighting, and surface strength to ensure safe operations.
-
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 district
An airport district is a designated urban or regional area surrounding an airport that integrates aviation facilities with commercial, industrial, and transportation infrastructure to support air travel and related economic activities.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:04 a.m.