Triple
T7331705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollywood Burbank Airport |
E169015
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | KBUR |
E169016
|
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: KBUR | Statement: [Hollywood Burbank Airport, ICAO code, KBUR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KBUR Context triple: [Hollywood Burbank Airport, ICAO code, KBUR]
-
A.
KBUR
chosen
KBUR is the ICAO airport code for Hollywood Burbank Airport, a commercial airport serving the Los Angeles area in Southern California.
-
B.
KBNA
KBNA is the ICAO airport code for Nashville International Airport, a major commercial airport serving Nashville, Tennessee.
-
C.
KRDG
KRDG is the ICAO airport code for Reading Regional Airport, a public airport serving Reading, Pennsylvania, in the United States.
-
D.
KCBF
KCBF is the ICAO airport code for Council Bluffs Municipal Airport in Council Bluffs, Iowa, United States.
-
E.
KBOI
KBOI is the ICAO airport code for Boise Airport, a commercial and general aviation airport serving Boise, Idaho.
- 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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0bf93dc8190931c13865ba827dd |
completed | March 27, 2026, 9:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7ef1ac84c819095f03cf731f11c01 |
completed | March 28, 2026, 3:09 p.m. |
Created at: March 27, 2026, 3:03 p.m.