Triple
T33000158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IATA airport code |
E844341
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation code standard |
C28043
|
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: aviation code standard Context triple: [IATA airport code, instanceOf, aviation code standard]
-
A.
aviation coding system
chosen
An aviation coding system is a structured set of standardized codes and rules used to represent, transmit, and interpret aviation-related information such as airports, routes, aircraft, and procedures in a consistent, machine-readable form.
-
B.
ICAO standard
An ICAO standard is an internationally agreed set of rules, specifications, and recommended practices established by the International Civil Aviation Organization to ensure the safety, regularity, and efficiency of global civil aviation.
-
C.
aviation standards organization
An aviation standards organization is an entity that develops, maintains, and promotes technical, safety, and operational standards to ensure interoperability, reliability, and safety across the aviation industry.
-
D.
air transport industry standard
A formalized set of rules, guidelines, and technical specifications that ensure safety, interoperability, efficiency, and regulatory compliance across the global air transport industry.
-
E.
ICAO airport code
An ICAO airport code is a four-letter alphanumeric identifier assigned by the International Civil Aviation Organization to uniquely designate airports and aerodromes worldwide for aviation operations and navigation.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.