Triple
T14867250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budapest Ferenc Liszt International Airport |
E349647
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | LHBP |
E349647
|
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: LHBP | Statement: [Budapest Ferenc Liszt International Airport, ICAOCode, LHBP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LHBP Context triple: [Budapest Ferenc Liszt International Airport, ICAOCode, LHBP]
-
A.
LHBP
chosen
LHBP is the ICAO airport code for Budapest Ferenc Liszt International Airport, the main international gateway to Hungary’s capital.
-
B.
LHPA
LHPA is the ICAO airport code for Pápa Air Base, a military airfield in Hungary.
-
C.
LH
LH is the two-letter IATA airline designator used to identify Lufthansa flights in global aviation systems.
-
D.
LH
The LH is a mid-1970s generation of the Holden Torana, an Australian compact car series known for its performance-oriented variants and motorsport success.
-
E.
LHM
LHM is the station code for Lillehammer railway station in Norway.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5776b848190bfe3a06ff261dc31 |
completed | April 15, 2026, 12:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe6b5101a48190937a86b6eda79c55 |
completed | May 8, 2026, 11:01 p.m. |
Created at: April 10, 2026, 1:55 a.m.