Triple
T26476463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 18 |
E666049
|
entity |
| Predicate | runwayNumberingStandard |
P55035
|
FINISHED |
| Object | ICAO runway numbering convention |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: ICAO runway numbering convention | Statement: [Runway 18, runwayNumberingStandard, ICAO runway numbering convention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayNumberingStandard Context triple: [Runway 18, runwayNumberingStandard, ICAO runway numbering convention]
-
A.
usesRunwayNumberingConvention
chosen
Indicates that an airport or runway follows a specific standardized system for assigning runway identification numbers.
-
B.
runwayFormat
Indicates the specific physical configuration or layout type of a runway used for takeoff and landing.
-
C.
hasRunwayNumberRange
Indicates that an entity (such as an airport or airfield) has runways whose identification numbers fall within a specified numeric range.
-
D.
hasRunwayNumber
Indicates that an airport or airfield runway is assigned a specific identifying number.
-
E.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
- F. None of above.
Provenance (3 batches)
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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 12:23 a.m.