Triple
T14790265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pellston Regional Airport |
E347634
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | KPLN |
E347635
|
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: KPLN | Statement: [Pellston Regional Airport, ICAO code, KPLN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KPLN Context triple: [Pellston Regional Airport, ICAO code, KPLN]
-
A.
KPLN
chosen
KPLN is the ICAO airport code for Pellston Regional Airport in Pellston, Michigan, United States.
-
B.
LKP
LKP was a Dutch World War II resistance organization composed of armed groups that carried out sabotage, raids, and support operations against the German occupation.
-
C.
KBLI
KBLI is the ICAO airport code for Bellingham International Airport in Bellingham, Washington, United States.
-
D.
LKL
LKL is the premier professional basketball league in Lithuania, featuring the country’s top clubs and serving as its highest level of domestic competition.
-
E.
QLK
QLK is the ICAO airline designator used for QantasLink, the regional brand of Australian airline Qantas.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd5d134c819080ee788b2e34163a |
completed | April 14, 2026, 11:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe24bc8464819096b019f1e927d1a9 |
completed | May 8, 2026, 6 p.m. |
Created at: April 10, 2026, 1:31 a.m.