Triple
T7365864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaohsiung International Airport |
E169866
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | RCKH |
E658142
|
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: RCKH | Statement: [Kaohsiung International Airport, hasCode, RCKH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RCKH Context triple: [Kaohsiung International Airport, hasCode, RCKH]
-
A.
RCKH
chosen
RCKH is the ICAO airport code for Kaohsiung International Airport, a major commercial airport serving Kaohsiung in southern Taiwan.
-
B.
RKC
RKC is the commonly used abbreviation for the Revised Kyoto Convention, an international agreement that standardizes and simplifies customs procedures worldwide.
-
C.
RKA
RKA is the Russian Space Agency that managed Russia’s human spaceflight activities, including operations of the Mir space station.
-
D.
RKR
RKR is the vehicle registration code assigned to vehicles registered in the Rymanów area of Poland.
-
E.
KRH
KRH is the commonly used abbreviation for the King’s Royal Hussars, a British Army cavalry regiment.
- 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f163038481909dedbffb4ae7f860 |
completed | March 27, 2026, 9:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c802b90cc081908b15e61921d15b92 |
completed | March 28, 2026, 4:32 p.m. |
Created at: March 27, 2026, 3:06 p.m.