Triple
T5913855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rental car center at Phoenix Sky Harbor International Airport |
E131529
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport-related building |
C19544
|
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-related building Context triple: [Rental car center at Phoenix Sky Harbor International Airport, instanceOf, airport-related building]
-
A.
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.
-
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 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.
-
D.
airport system
An airport system is an integrated network of facilities, services, and processes that manages the safe, efficient movement of passengers, cargo, and aircraft within and around an airport.
-
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. 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:59 p.m.