Triple
T16724154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICAO Annex 14 (general runway designation rules) |
E406426
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | runway designation 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: runway designation standard Context triple: [ICAO Annex 14 (general runway designation rules), instanceOf, runway designation standard]
-
A.
runway end designation
A runway end designation is the alphanumeric identifier assigned to one end of a runway, typically based on its magnetic heading, used to distinguish it from the opposite end and aid in navigation and operations.
-
B.
airport runway
An airport runway is a long, specially prepared strip of land or pavement where aircraft take off and land, designed with specific markings, lighting, and surface strength to ensure safe operations.
-
C.
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.
-
D.
radiotelephony designator
A radiotelephony designator is a standardized spoken identifier assigned to an aircraft operator, airline, or aviation service for use in voice radio communications.
-
E.
parallel runway
A parallel runway is one of two or more runways at an airport that are aligned in the same direction and used simultaneously or independently to increase traffic capacity and operational efficiency.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.