Triple
T12032450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IATA Passenger Distribution initiatives |
E286445
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airline industry program |
C11420
|
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: airline industry program Context triple: [IATA Passenger Distribution initiatives, instanceOf, airline industry program]
-
A.
IATA program
chosen
An IATA program is an organized set of standards, training, and regulatory frameworks developed by the International Air Transport Association to enhance safety, efficiency, and consistency across global air transport operations.
-
B.
airport service program
An airport service program is a coordinated set of services and processes designed to manage and enhance passenger, baggage, and aircraft handling throughout all stages of airport operations.
-
C.
frequent-flyer program
A frequent-flyer program is a customer loyalty scheme offered by an airline that rewards passengers with points or miles for their flights and related purchases, which can be redeemed for benefits such as free flights, upgrades, and priority services.
-
D.
airline loyalty program
An airline loyalty program is a customer rewards system that allows passengers to earn and redeem points or miles for flights and related travel benefits based on their travel activity and tier status.
-
E.
airline safety audit program
A structured, systematic process used by airlines or regulators to evaluate and verify an airline’s compliance with safety standards, operational procedures, and risk management practices to ensure safe flight operations.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.