Triple
T19637603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Luis Valley Regional Airport |
E471440
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | KALS |
—
|
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: KALS | Statement: [San Luis Valley Regional Airport, ICAOcode, KALS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KALS Context triple: [San Luis Valley Regional Airport, ICAOcode, KALS]
-
A.
KALS
chosen
KALS is the ICAO airport code for San Luis Valley Regional Airport serving Alamosa, Colorado.
-
B.
KLSI
KLSI is the ICAO airport code assigned to Ellsworth Air Force Base in South Dakota, a major United States Air Force installation.
-
C.
KALB
KALB is the ICAO airport code for Albany International Airport, a major commercial airport serving New York’s Capital Region.
-
D.
KELW
KELW is a radio station in the United States that previously operated under the call sign KLAC.
-
E.
KSLC
KSLC is the ICAO airport code for Salt Lake City International Airport, a major air transportation hub serving Salt Lake City, Utah.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64107f3fc8190ace6ae67287d280c |
completed | April 20, 2026, 3:06 p.m. |
Created at: April 10, 2026, 1:44 p.m.