Triple
T19511350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taiz International Airport |
E488160
|
entity |
| Predicate | hasRunway |
P105
|
FINISHED |
| Object | Runway 01/19 |
—
|
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 01/19 | Statement: [Taiz International Airport, hasRunway, Runway 01/19]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway 01/19 Context triple: [Taiz International Airport, hasRunway, Runway 01/19]
-
A.
Runway 01/19
chosen
Runway 01/19 is a primary paved runway at Niagara District Airport used for aircraft takeoffs and landings aligned roughly north–south.
-
B.
Runway 02/20
Runway 02/20 is the primary paved runway at Iki Airport in Nagasaki Prefecture, Japan, used for regional domestic flights.
-
C.
Runway 02/20
Runway 02/20 is a principal landing and takeoff strip at Carriel Sur International Airport in Chile, aligned roughly along the 020/200-degree magnetic headings.
-
D.
Runway 02/20
Runway 02/20 is one of the primary paved runways at Richmond International Airport, used for handling a range of commercial and general aviation traffic.
-
E.
Runway 02/20
Runway 02/20 is one of the primary paved runways at Edmonton International Airport, aligned roughly north–south to accommodate various wind conditions and aircraft operations.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63516572c8190a8719c51fd3f7147 |
completed | April 20, 2026, 2:15 p.m. |
Created at: April 10, 2026, 1:40 p.m.