Triple
T15810664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 15R/33L |
E383340
|
entity |
| Predicate | identifiedByICAORunwayDesignator |
P54806
|
FINISHED |
| Object | 15R/33L |
—
|
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: 15R/33L | Statement: [15R/33L, identifiedByICAORunwayDesignator, 15R/33L]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiedByICAORunwayDesignator Context triple: [15R/33L, identifiedByICAORunwayDesignator, 15R/33L]
-
A.
isPrimaryRunwayOf
Indicates that a runway serves as the main or principal runway for a particular airport or airfield.
-
B.
hasRunwayDesignationSide
chosen
Indicates that a runway designation is associated with a specific side or direction of the runway (e.g., left, right, or center).
-
C.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
-
D.
ICAOTypeDesignator
Indicates the standardized aircraft type code assigned by ICAO that specifies the model or family of an aircraft used in aviation operations and documentation.
-
E.
airportDesignation
Indicates that an entity is officially designated or classified as an airport.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b52aae14819091de08630e7e1d1a |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.