Triple
T20945738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ketchikan International Airport |
E515838
|
entity |
| Predicate | uses |
P98
|
FINISHED |
| Object | PAKT |
—
|
NE NERFINISHED |
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: PAKT | Statement: [Ketchikan International Airport, uses, PAKT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PAKT Context triple: [Ketchikan International Airport, uses, PAKT]
-
A.
PAKT
chosen
PAKT is the ICAO airport code for Ketchikan International Airport, a public airport serving Ketchikan in southeastern Alaska, United States.
-
B.
PKT
PKT is the commonly used abbreviation for PKT Gdynia, a public transport operator based in Gdynia, Poland.
-
C.
PKT
PKT is the time zone used throughout Pakistan, corresponding to UTC+5 hours.
-
D.
Pak
Pak is an alternative name for Lemerig, a nearly extinct Oceanic language spoken in northern Vanuatu.
-
E.
Pak
Pak are a fictional alien species from Larry Niven’s Known Space universe, characterized by their three-stage life cycle and hyper-intelligent, hyper-protective "Protector" phase.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fad7f67481908675e76736f5e0c3 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 12:56 p.m.