Triple
T1001247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KPHX |
E21606
|
entity |
| Predicate | hasRunway |
P105
|
FINISHED |
| Object | Runway 07L/25R |
E87182
|
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 07L/25R | Statement: [KPHX, hasRunway, Runway 07L/25R]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway 07L/25R Context triple: [KPHX, hasRunway, Runway 07L/25R]
-
A.
Runway 07L/25R
chosen
Runway 07L/25R is a designated airport runway forming one of a pair of parallel runways used for aircraft takeoffs and landings.
-
B.
Runway 07R/25L
Runway 07R/25L is one of the primary east–west runways at Los Angeles International Airport, used for handling a high volume of commercial air traffic.
-
C.
Runway 05L/23R
Runway 05L/23R is one of the main parallel runways at Manchester Airport, used for handling a high volume of commercial air traffic.
-
D.
Runway 05R/23L
Runway 05R/23L is one of the main parallel runways at Manchester Airport in the United Kingdom, used for handling commercial air traffic.
-
E.
Runway 09L/27R
Runway 09L/27R is a major east–west runway at Chicago O'Hare International Airport used for handling high volumes of commercial air traffic.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4fb18b88190ae2d620aaaff4f90 |
completed | March 1, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac537d788c81908d239f102626bdd6 |
completed | March 7, 2026, 4:34 p.m. |
Created at: March 1, 2026, 7:41 p.m.