Triple
T33757298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hong Kong FIR |
E865012
|
entity |
| Predicate | hasPrimaryAirportIcaoCode |
P155924
|
FINISHED |
| Object | VHHH |
E246646
|
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: VHHH | Statement: [Hong Kong FIR, hasPrimaryAirportIcaoCode, VHHH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryAirportIcaoCode Context triple: [Hong Kong FIR, hasPrimaryAirportIcaoCode, VHHH]
-
A.
hasPrimaryAirportRole
Indicates that an entity holds the main or principal functional role associated with an airport.
-
B.
hasIcaoAirport
chosen
Indicates that an entity is associated with an airport identified by a specific ICAO (International Civil Aviation Organization) airport code.
-
C.
operatorPrimaryHubAirportCode
Indicates the airport code of the main or primary hub used by the operator.
-
D.
ICAOcode
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
E.
isMajorDomesticAirportCode
Indicates that an airport code belongs to a major domestic airport within a given country or region.
- F. None of above.
Provenance (4 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01c74a72fc819084826c6c292af03a |
completed | May 11, 2026, 12:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366579511c81909d2647c1f4279cae |
completed | June 20, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a01c624103c819087cb35a71c5868b6 |
completed | May 11, 2026, 12:05 p.m. |
Created at: May 1, 2026, 1:45 a.m.