Triple
T10964750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IATA Resolution 762 |
E259066
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IATA resolution |
C28399
|
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: IATA resolution Context triple: [IATA Resolution 762, instanceOf, IATA resolution]
-
A.
IATA system
The IATA system is a standardized global framework established by the International Air Transport Association to regulate, coordinate, and facilitate commercial air transport operations, including airline codes, ticketing, safety, and international travel procedures.
-
B.
IATA program
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.
-
C.
airline association
An airline association is an organized group of airlines that collaborates to set industry standards, coordinate policies, and advocate for the collective interests of its member carriers.
-
D.
implementation mechanism for ICAO Standards and Recommended Practices
A structured set of legal, administrative, and technical processes through which States adopt, adapt, and apply ICAO Standards and Recommended Practices within their national civil aviation systems.
-
E.
IATA flight number
An IATA flight number is a standardized alphanumeric code assigned by an airline, consisting of a two-character airline designator followed by a 1–4 digit number, used to identify a specific scheduled flight in timetables, tickets, and air traffic systems.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:24 p.m.