Triple
T14929378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 06/24 |
E372217
|
entity |
| Predicate | runwayEnd |
P8863
|
FINISHED |
| Object | Runway 24 |
E776877
|
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 24 | Statement: [Runway 06/24, runwayEnd, Runway 24]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway 24 Context triple: [Runway 06/24, runwayEnd, Runway 24]
-
A.
Runway 24
chosen
Runway 24 is one of the primary landing and takeoff runways at Jomo Kenyatta International Airport in Nairobi, Kenya.
-
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 22
Runway 22 is the runway end aligned approximately with a 220-degree magnetic heading, commonly used for aircraft takeoffs and landings in that direction.
-
E.
Runway 36L
Runway 36L is the northern, left-hand end of a major north–south runway used for aircraft takeoffs and landings at an airport.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded634e67881909daec9eaef188d09 |
completed | April 15, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feae048fa08190ba5719ca9868b50d |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 2:36 a.m.