Triple
T12525355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aktobe International Airport |
E299422
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | AKX |
E299423
|
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: AKX | Statement: [Aktobe International Airport, IATAcode, AKX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AKX Context triple: [Aktobe International Airport, IATAcode, AKX]
-
A.
AKX
chosen
AKX is the IATA airport code for Aktobe International Airport in Aktobe, Kazakhstan.
-
B.
AKX
AKX is the ICAO airline designator assigned to ANA Wings, a regional subsidiary of All Nippon Airways in Japan.
-
C.
AXJ
AXJ is the IATA airport code for Amakusa Airfield, a regional airport serving the Amakusa Islands in Kumamoto Prefecture, Japan.
-
D.
AKH
AKH is the FAA location identifier for Gastonia Municipal Airport, a public airport serving Gastonia, North Carolina.
-
E.
AXS
AXS is a digital ticketing and event management platform known for selling and distributing tickets for sports, concerts, and live entertainment events.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9545d7e6c819080c3a85c18caa1ae |
completed | April 10, 2026, 7:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f64bc393808190add527030a928517 |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 8, 2026, 9:57 p.m.