Triple
T10460337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Hong Kong |
E246654
|
entity |
| Predicate | ICAO airline designator |
P36333
|
FINISHED |
| Object | AHK |
E246654
|
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: AHK | Statement: [Air Hong Kong, ICAO airline designator, AHK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AHK Context triple: [Air Hong Kong, ICAO airline designator, AHK]
-
A.
AHK
chosen
AHK is the ICAO airline designator for Air Hong Kong, a cargo airline based in Hong Kong.
-
B.
AHX
AHX is the ICAO airline designator assigned to Amakusa Airlines, a regional carrier based in Japan.
-
C.
AHO
AHO is the IATA airport code for Alghero-Fertilia Airport, a commercial airport serving the city of Alghero and the surrounding region in Sardinia, Italy.
-
D.
ARexx
ARexx is a REXX-based scripting language for the AmigaOS platform, commonly used to automate tasks and enable inter-application communication.
-
E.
AH1
AH1 is a major route in the Asian Highway Network that runs from Tokyo, Japan, through multiple Asian countries to the border between Turkey and Bulgaria in Europe.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50882eb0c8190a4311634b867eab1 |
completed | April 7, 2026, 1:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d89fcc84b48190a39de0d9b9111ebd |
completed | April 10, 2026, 6:59 a.m. |
Created at: April 6, 2026, 12:18 p.m.