Triple
T21625797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurukun Airport |
E533697
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | AUU |
—
|
NE NERFINISHED |
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: AUU | Statement: [Aurukun Airport, IATA code, AUU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AUU Context triple: [Aurukun Airport, IATA code, AUU]
-
A.
AUU
chosen
AUU is the IATA airport code for Aurukun Airport, which serves the remote community of Aurukun in Queensland, Australia.
-
B.
UAAA
UAAA is the ICAO airport code for Almaty International Airport, the main air gateway to Almaty, Kazakhstan.
-
C.
AÜ
AÜ is the commonly used abbreviation for Ankara University, a major public research university in Turkey’s capital city.
-
D.
KUU
KUU is the IATA airport code for Kullu–Manali Airport, a regional airport serving the Kullu and Manali regions in the Indian state of Himachal Pradesh.
-
E.
AArU
AArU is a regional organization that brings together universities from Arab countries to promote cooperation, coordination, and development in higher education and research.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52131f2c8190b9966adf43a0fe4f |
completed | April 27, 2026, 12:09 p.m. |
Created at: April 16, 2026, 6:34 p.m.