Triple
T13638779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elmdon Airport |
E325919
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | BHX |
E325917
|
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: BHX | Statement: [Elmdon Airport, IATAcode, BHX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BHX Context triple: [Elmdon Airport, IATAcode, BHX]
-
A.
BHX
chosen
BHX is the three-letter IATA airport code for Birmingham Airport in the United Kingdom.
-
B.
BHY
BHY is the IATA airport code for Beihai Fucheng Airport, a commercial airport serving Beihai in Guangxi, China.
-
C.
BX
BX is the IATA airline designator for Air Busan, a South Korean low-cost carrier based in Busan.
-
D.
BX
BX is the stock ticker symbol for Blackstone Inc., a leading global alternative asset management firm specializing in private equity, real estate, credit, and hedge fund solutions.
-
E.
BXM
BXM is the railway station code for Brussels-South (Bruxelles-Midi / Brussel-Zuid), the main international and domestic rail hub in Brussels, Belgium.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5a84cc4819098a975e33250c89b |
completed | April 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7943306f08190b3a4c44e5b22db0a |
completed | May 3, 2026, 6:30 p.m. |
Created at: April 9, 2026, 9:51 p.m.