Triple

T21948761
Position Surface form Disambiguated ID Type / Status
Subject Zhengzhou Xinzheng International Airport E542005 entity
Predicate hubFor P423 FINISHED
Object Lucky Air 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: Lucky Air | Statement: [Zhengzhou Xinzheng International Airport, hubFor, Lucky Air]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lucky Air
Context triple: [Zhengzhou Xinzheng International Airport, hubFor, Lucky Air]
  • A. Lucky Air chosen
    Lucky Air is a Chinese low-cost airline based in Yunnan Province that operates domestic and regional flights across China and nearby countries.
  • B. Buddha Air
    Buddha Air is a prominent Nepalese domestic airline known for operating scheduled flights and mountain sightseeing tours, particularly around the Himalayas.
  • C. Belau Air
    Belau Air is a small regional airline based in Palau that operates domestic and nearby international flights, primarily serving local island communities.
  • D. Loong Air
    Loong Air is a Chinese passenger and cargo airline based in Hangzhou that operates domestic and regional routes across Asia.
  • E. Dragonair
    Dragonair was a Hong Kong-based regional airline, later rebranded as Cathay Dragon, that primarily operated flights within Asia.
  • 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_69e0c47ef0e48190a50e1bcc43f4b3fd completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1243a2f788190bd4625fa79888696 completed April 28, 2026, 9:18 p.m.
Created at: April 16, 2026, 7:58 p.m.