Triple
T33650534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICAO telephony designator system |
E862086
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation communication 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: aviation communication standard Context triple: [ICAO telephony designator system, instanceOf, aviation communication 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.
radiotelephony pronunciation
Radiotelephony pronunciation is the standardized system of speaking letters, numbers, and procedural words over radio communications to ensure clarity and prevent misunderstandings.
-
C.
aviation convention
An aviation convention is a large organized gathering of aviation professionals, enthusiasts, and industry stakeholders to showcase aircraft, technologies, services, and to exchange knowledge through exhibitions, presentations, and networking events.
-
D.
radio call sign convention
A radio call sign convention is a standardized system of assigning and formatting unique identifiers to radio stations or operators to ensure clear, organized, and internationally recognizable communication.
-
E.
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.
- 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.