Triple
T6058370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yelizovo Airport |
E134969
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | PKC |
E561204
|
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: PKC | Statement: [Yelizovo Airport, IATAcode, PKC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PKC Context triple: [Yelizovo Airport, IATAcode, PKC]
-
A.
PKC
PKC is a leading international cryptography conference focused on public-key cryptography research and advancements.
-
B.
PKC
chosen
PKC is the IATA airport code for Petropavlovsk-Kamchatsky Airport, a major air gateway to Russia’s Kamchatka Peninsula.
-
C.
PKB
PKB is the IATA airport code for Mid-Ohio Valley Regional Airport serving the Parkersburg–Vienna area in West Virginia, USA.
-
D.
PK
PK is the two-letter ISO 3166-1 alpha-2 country code that uniquely identifies Pakistan in international standards and systems.
-
E.
PK
PK is a compact bitmap font file format traditionally used by TeX systems to store rasterized glyphs generated from METAFONT sources.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570e64408190ae7a2504f63bb58a |
completed | March 22, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11d0e06288190b4389b43825d5929 |
completed | March 23, 2026, 10:59 a.m. |
Created at: March 22, 2026, 4:10 p.m.