Triple
T13827250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 18R/36L |
E332281
|
entity |
| Predicate | belongsToAirportWithICAOCode |
P36333
|
FINISHED |
| Object | KMEM |
E251306
|
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: KMEM | Statement: [Runway 18R/36L, belongsToAirportWithICAOCode, KMEM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KMEM Context triple: [Runway 18R/36L, belongsToAirportWithICAOCode, KMEM]
-
A.
KMEM
chosen
KMEM is the ICAO airport code for Memphis International Airport, a major cargo and passenger hub in Memphis, Tennessee.
-
B.
KMEV
KMEV is the ICAO airport code for Minden–Tahoe Airport, a public general aviation airport serving the Minden and Lake Tahoe region in Nevada, United States.
-
C.
KMCE
KMCE is the ICAO airport code for Merced Regional Airport, a public airport serving Merced, California.
-
D.
KV
KV is the vehicle registration code used on license plates for vehicles registered in Kraljevo, a city in central Serbia.
-
E.
KEM
KEM is the IATA airport code for Kemi-Tornio Airport in northern Finland.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0295d2d48190b08eba0d805bd72d |
completed | April 14, 2026, 9:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8ea22c081909cc34f1030a8589b |
completed | May 3, 2026, 9:06 p.m. |
Created at: April 9, 2026, 10:13 p.m.