Triple
T12287521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayers Rock Airport |
E292867
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | AYQ |
E292868
|
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: AYQ | Statement: [Ayers Rock Airport, IATAcode, AYQ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AYQ Context triple: [Ayers Rock Airport, IATAcode, AYQ]
-
A.
AYQ
chosen
AYQ is the IATA airport code for Ayers Rock (Connellan) Airport, which serves the Yulara resort area near Uluru in Australia’s Northern Territory.
-
B.
AYJ
AYJ is the IATA airport code for Maharishi Valmiki International Airport serving Ayodhya in Uttar Pradesh, India.
-
C.
AAY
AAY is the ICAO airline designator used to identify Allegiant Air in aviation operations and communications.
-
D.
AYT
AYT is the IATA airport code for Antalya Airport, a major international gateway serving the resort city of Antalya on Turkey’s Mediterranean coast.
-
E.
AYTO
AYTO is a reality dating competition series where singles try to identify their predetermined perfect matches to win a shared cash prize.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d1ffb208190a4b86d7d4ceee045 |
completed | April 10, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e7315608190963c714a0b128dbb |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:52 p.m.