Triple
T6637016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milan Bergamo Airport |
E150482
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | BGY |
E150482
|
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: BGY | Statement: [Milan Bergamo Airport, IATA code, BGY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BGY Context triple: [Milan Bergamo Airport, IATA code, BGY]
-
A.
BGY
chosen
BGY is the IATA airport code for Milan Bergamo Airport, a major low-cost and regional air travel hub serving the Milan metropolitan area in northern Italy.
-
B.
BG
BG is the two-letter ISO 3166-1 alpha-2 country code representing Bulgaria.
-
C.
BG
BG is the vehicle registration code used for Belgrade, the capital city of Serbia.
-
D.
BGs
BGs is an abbreviation commonly used to refer to the Bee Gees, the famous pop and disco music group formed by brothers Barry, Robin, and Maurice Gibb.
-
E.
BnG
BnG is the commonly used abbreviation for Bòrd na Gàidhlig, the principal public body responsible for promoting and supporting the Scottish Gaelic language in Scotland.
- 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_69c687f0ceb08190bf40807bfc605fa5 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6afcf439c8190b9334b34774da821 |
completed | March 27, 2026, 4:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6cbf71874819080cc89b6740b1567 |
completed | March 27, 2026, 6:27 p.m. |
Created at: March 27, 2026, 1:59 p.m.