Triple
T4033275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuala Lumpur International Airport |
E83764
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | KUL |
E318232
|
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: KUL | Statement: [Kuala Lumpur International Airport, IATAcode, KUL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KUL Context triple: [Kuala Lumpur International Airport, IATAcode, KUL]
-
A.
KUL
chosen
KUL is the IATA airport code for Kuala Lumpur International Airport, the main international gateway serving Malaysia’s capital region.
-
B.
KAL
KAL is the ICAO airline designator used to identify Korean Air in international aviation operations.
-
C.
KLu
KLu is the commonly used abbreviation for the Royal Netherlands Air Force, the aerial warfare branch of the Dutch armed forces.
-
D.
CUL
CUL is the main research library of the University of Cambridge and one of the largest and most important academic libraries in the United Kingdom.
-
E.
KL
KL is the two-letter IATA airline code assigned to KLM Royal Dutch Airlines.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb108fc0819080c8f41da2e558e0 |
completed | March 9, 2026, 4:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5563e11708190abc9ba55b1be43a5 |
completed | March 14, 2026, 12:36 p.m. |
Created at: March 9, 2026, 3:36 p.m.