Triple
T13310952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohhot Baita International Airport |
E317061
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | ZBHH |
E1032840
|
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: ZBHH | Statement: [Hohhot Baita International Airport, hasCode, ZBHH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ZBHH Context triple: [Hohhot Baita International Airport, hasCode, ZBHH]
-
A.
ZBHH
chosen
ZBHH is the ICAO airport code for Hohhot Baita International Airport, a major air transport hub serving Hohhot in Inner Mongolia, China.
-
B.
ZBH
ZBH is the stock ticker symbol for Zimmer Biomet Holdings, Inc., a major medical device company specializing in musculoskeletal healthcare products.
-
C.
ZGBH
ZGBH is the ICAO airport code for Beihai Fucheng Airport, a commercial airport serving Beihai in Guangxi, China.
-
D.
ZBSJ
ZBSJ is the ICAO airport code for Shijiazhuang Zhengding International Airport, a major air transport hub serving Shijiazhuang in Hebei Province, China.
-
E.
GZB
GZB is the station code for Ghaziabad Junction, a major railway hub in the Indian state of Uttar Pradesh.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d990f56abc8190951774a999e2ce11 |
completed | April 11, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f71f2810a881908b1ed0cc4fb9ac12 |
completed | May 3, 2026, 10:10 a.m. |
Created at: April 9, 2026, 9:29 p.m.