Triple
T16936261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antalya Airport |
E410833
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | AYT |
E84719
|
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: AYT | Statement: [Antalya Airport, IATA code, AYT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AYT Context triple: [Antalya Airport, IATA code, AYT]
-
A.
AYT
chosen
AYT is the IATA airport code for Antalya Airport, a major international gateway serving the resort city of Antalya on Turkey’s Mediterranean coast.
-
B.
AYTO
AYTO is a reality dating competition series where singles try to identify their predetermined perfect matches to win a shared cash prize.
-
C.
AAY
AAY is the ICAO airline designator used to identify Allegiant Air in aviation operations and communications.
-
D.
ATY
ATY is the regional code used to designate Atyrau, an oil-rich region and city in western Kazakhstan located near the Caspian Sea.
-
E.
ATY
ATY is the stock ticker symbol for ATI Technologies, a former Canadian graphics processing unit and chipset manufacturer later acquired by AMD.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2a05f48190a0a8ac86985f4000 |
completed | April 18, 2026, 6:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00cfe2d4f48190b965b6c0a3cc0125 |
completed | May 10, 2026, 6:35 p.m. |
Created at: April 10, 2026, 5:30 a.m.