Triple
T2764571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 04/22 |
E61303
|
entity |
| Predicate | hasRunwayEnd |
P8863
|
FINISHED |
| Object | Runway 22 |
E177898
|
NE 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: Runway 22 | Statement: [Runway 04/22, hasRunwayEnd, Runway 22]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway 22 Context triple: [Runway 04/22, hasRunwayEnd, Runway 22]
-
A.
Runway 22
chosen
Runway 22 is the runway end aligned approximately with a 220-degree magnetic heading, commonly used for aircraft takeoffs and landings in that direction.
-
B.
Runway 21
Runway 21 is one of the primary landing and takeoff runways serving Charles B. Wheeler Downtown Airport in Kansas City, Missouri.
-
C.
Runway 19
Runway 19 is one of the primary landing and takeoff runways serving Charles B. Wheeler Downtown Airport in Kansas City, Missouri.
-
D.
Runway 5
Runway 5 is an airport runway designation indicating an approximate magnetic heading of 50 degrees, typically used when runway numbers are updated to reflect shifts in Earth’s magnetic variation.
-
E.
Runway 17
Runway 17 is a designated Space Shuttle landing runway used for the touchdown of NASA missions such as STS-26.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab4b7bab6c8190a5c2efef19a8ef34 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdd541c2c8190a983a6f6a0b24ed9 |
completed | March 7, 2026, 8:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b53fc6f4b48190aebcf7457b6d670d |
completed | March 14, 2026, 11 a.m. |
Created at: March 6, 2026, 9:57 p.m.