Triple
T14589904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andijan Airport |
E342415
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | AZN |
E342416
|
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: AZN | Statement: [Andijan Airport, IATA code, AZN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AZN Context triple: [Andijan Airport, IATA code, AZN]
-
A.
AZN
chosen
AZN is the IATA airport code for Andijan Airport, a regional air transport hub serving the city of Andijan in eastern Uzbekistan.
-
B.
AZN
AZN is the stock ticker symbol for AstraZeneca, a major global biopharmaceutical company known for developing prescription medicines across several therapeutic areas.
-
C.
AZU
AZU is the ICAO airline designator for Azul Brazilian Airlines, a major low-cost carrier based in Brazil.
-
D.
AZD
AZD is a common shorthand used to refer to the Arizona Diamondbacks, a Major League Baseball team based in Phoenix, Arizona.
-
E.
Azna
Azna is a small city in western Iran known for its location in the mountainous Lorestan region and its role as a local administrative and commercial center.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4237d88819097f3f9a40f5be152 |
completed | April 14, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd94c36bb881909af16aa1df1766f8 |
completed | May 8, 2026, 7:46 a.m. |
Created at: April 10, 2026, 1:24 a.m.