Triple
T21378446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 13/31 |
E527275
|
entity |
| Predicate | hasRunwayEnd |
P8863
|
FINISHED |
| Object | Runway 13 |
—
|
NE NERFINISHED |
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 13 | Statement: [Runway 13/31, hasRunwayEnd, Runway 13]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway 13 Context triple: [Runway 13/31, hasRunwayEnd, Runway 13]
-
A.
Runway 13
chosen
Runway 13 is one end of an airport runway aligned approximately on a 130-degree magnetic heading, typically used for aircraft takeoffs and landings in that direction.
-
B.
Runway 2
Runway 2 is one end of an airport runway designated with the heading “02,” typically aligned roughly toward 020 degrees on the compass.
-
C.
Runway 3
Runway 3 is an airport runway designation indicating a magnetic heading of approximately 030 degrees, used to guide aircraft during takeoff and landing.
-
D.
Runway 4
Runway 4 is one end of a bidirectional airport runway, typically aligned toward a magnetic heading of approximately 040 degrees.
-
E.
Runway 19
Runway 19 is one of the primary landing and takeoff runways serving Charles B. Wheeler Downtown Airport in Kansas City, Missouri.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51f363c8190944000ab5523b02b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0ca5e1c81909b06958459c553dc |
completed | April 22, 2026, 11:28 a.m. |
Created at: April 16, 2026, 5:11 p.m.