Triple
T358180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Navigation Commission |
E7590
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation standards-making body |
C904
|
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 standards-making body Context triple: [Air Navigation Commission, instanceOf, aviation standards-making body]
-
A.
aircraft observation organisation
An aircraft observation organisation is an entity responsible for systematically monitoring, recording, and analyzing aircraft movements and related airspace activities for purposes such as safety, research, regulation, or intelligence.
-
B.
technical standards body
chosen
A technical standards body is an organization that develops, maintains, and promotes agreed-upon technical specifications and protocols to ensure interoperability, safety, and consistency across industries and technologies.
-
C.
airport authority
An airport authority is an organization responsible for the ownership, management, operation, and regulation of an airport or group of airports, ensuring safe, efficient, and compliant aviation services and facilities.
-
D.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.