Triple
T13441868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Paul II International Airport Kraków–Balice |
E320381
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | KRK |
E320380
|
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: KRK | Statement: [John Paul II International Airport Kraków–Balice, IATACode, KRK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KRK Context triple: [John Paul II International Airport Kraków–Balice, IATACode, KRK]
-
A.
KRK
chosen
KRK is the IATA airport code for John Paul II International Airport Kraków–Balice, the main international airport serving Kraków, Poland.
-
B.
CRK
CRK is the National Rail station code for Chirk railway station in Wrexham, Wales.
-
C.
CRK
CRK is the IATA airport code for Clark International Airport, a major aviation hub located in Pampanga, Philippines.
-
D.
RKR
RKR is the vehicle registration code assigned to vehicles registered in the Rymanów area of Poland.
-
E.
KRU
KRU is a German vehicle registration code assigned to the district of Günzburg in the state of Bavaria.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee704ac8190b4c7f4e0d3a88494 |
completed | April 12, 2026, 2:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7399421908190a7750e37c89a73f6 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 9, 2026, 9:40 p.m.