Triple
T35163849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Dhabi Duty Free |
E1015339
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport retail company |
C16943
|
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 retail company Context triple: [Abu Dhabi Duty Free, instanceOf, airport retail company]
-
A.
airport retail operator
chosen
An airport retail operator is a business entity that manages and runs commercial retail outlets within airport terminals, offering goods and services to travelers and airport staff under specific concession agreements.
-
B.
airport services provider
An airport services provider is an organization that delivers ground handling, passenger assistance, cargo management, and related operational support services to airlines and airport authorities.
-
C.
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.
-
D.
airport consultancy company
A specialized professional services firm that advises airports and aviation stakeholders on planning, design, operations, strategy, and regulatory compliance to optimize performance and growth.
-
E.
airport IT solutions provider
An airport IT solutions provider is a specialized company that designs, implements, and maintains integrated technology systems to optimize airport operations, enhance passenger experience, and ensure secure, efficient management of airport infrastructure and services.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.