Triple
T20899054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concourse E checkpoint |
E514619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport security checkpoint |
C3499
|
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 security checkpoint Context triple: [Concourse E checkpoint, instanceOf, airport security checkpoint]
-
A.
security checkpoint
chosen
A security checkpoint is a controlled access area where people, belongings, or vehicles are inspected to prevent unauthorized entry and ensure safety.
-
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.
Airport
An airport is a complex transportation hub where aircraft take off, land, are serviced, and passengers and cargo transition between air and ground travel through various terminals and support facilities.
-
D.
airport security screening program
An airport security screening program is a coordinated set of procedures, technologies, and personnel activities designed to inspect passengers, baggage, and cargo to prevent prohibited items and security threats from entering secure areas or aircraft.
-
E.
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.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:47 p.m.