Triple
T2251189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Hong Kong |
E49619
|
entity |
| Predicate | callsign |
P1565
|
FINISHED |
| Object | AIR HONG KONG |
E49619
|
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: AIR HONG KONG | Statement: [Air Hong Kong, callsign, AIR HONG KONG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AIR HONG KONG Context triple: [Air Hong Kong, callsign, AIR HONG KONG]
-
A.
Air Hong Kong
chosen
Air Hong Kong is a Hong Kong-based all-cargo airline that primarily operates regional freight services across Asia.
-
B.
Jin Air
Jin Air is a South Korean low-cost airline that operates domestic and international passenger flights.
-
C.
EVA Air
EVA Air is a major Taiwanese international airline known for its extensive global route network, high service standards, and innovative themed flights such as its Hello Kitty jets.
-
D.
Cathay Pacific
Cathay Pacific is a major Hong Kong-based international airline known for its extensive global network and premium full-service operations.
-
E.
Thai Airways International
Thai Airways International is the flag carrier airline of Thailand, operating an extensive network of domestic and international flights from its main hub in Bangkok.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc11d04688190abc04fac3a1804a9 |
completed | March 7, 2026, 6:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae6b1bc424819087b2ce9a6256a180 |
completed | March 9, 2026, 6:39 a.m. |
Created at: March 4, 2026, 7:47 p.m.