Triple
T6739620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beirut–Rafic Hariri International Airport |
E154041
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | BEY |
E154041
|
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: BEY | Statement: [Beirut–Rafic Hariri International Airport, IATA code, BEY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BEY Context triple: [Beirut–Rafic Hariri International Airport, IATA code, BEY]
-
A.
BEY
chosen
BEY is the IATA airport code for Beirut–Rafic Hariri International Airport, the main international gateway to Lebanon’s capital city.
-
B.
Bey
A Bey was a provincial governor or chieftain in the Ottoman Empire, often wielding significant military and administrative authority.
-
C.
BEK
BEK is the IATA airport code for Bareilly Airport, a domestic airport serving the city of Bareilly in Uttar Pradesh, India.
-
D.
BY
BY is the two-letter ISO 3166-1 alpha-2 country code assigned to Belarus.
-
E.
BY
BY is the IATA airline designator assigned to TUI Airways, a major UK-based leisure airline.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d187c8788190b9fc1ebc9a66a520 |
completed | March 27, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70b0db3f481909b5281c63cc32dd1 |
completed | March 27, 2026, 10:56 p.m. |
Created at: March 27, 2026, 2:10 p.m.