Triple
T33650536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICAO telephony designator system |
E862086
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air traffic management standard |
C7733
|
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: air traffic management standard Context triple: [ICAO telephony designator system, instanceOf, air traffic management standard]
-
A.
ICAO standard
chosen
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.
-
B.
air navigation organization
An air navigation organization is an entity responsible for planning, managing, and controlling the safe and efficient movement of aircraft through designated airspace using air traffic services, communication, navigation, and surveillance systems.
-
C.
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.
-
D.
flow management standard
A flow management standard defines the rules, processes, and guidelines for efficiently controlling, coordinating, and optimizing the movement of resources, information, or work through a system or network.
-
E.
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.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.