Triple
T20224776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid-Ohio Valley Regional Airport |
E495348
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | PKB |
—
|
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: PKB | Statement: [Mid-Ohio Valley Regional Airport, IATA code, PKB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PKB Context triple: [Mid-Ohio Valley Regional Airport, IATA code, PKB]
-
A.
PKB
chosen
PKB is the IATA airport code for Mid-Ohio Valley Regional Airport serving the Parkersburg–Vienna area in West Virginia, USA.
-
B.
PKC
PKC is a leading international cryptography conference focused on public-key cryptography research and advancements.
-
C.
PKC
PKC is the IATA airport code for Petropavlovsk-Kamchatsky Airport, a major air gateway to Russia’s Kamchatka Peninsula.
-
D.
KPKB
KPKB is the ICAO airport code for Mid-Ohio Valley Regional Airport, a public airport serving the Parkersburg–Vienna area in West Virginia, United States.
-
E.
PKP
PKP is Poland’s state-owned national railway operator, responsible for much of the country’s passenger and freight rail transport infrastructure.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd8f1948190adbb947a7870bb43 |
completed | April 20, 2026, 6:26 p.m. |
Created at: April 11, 2026, 11:39 p.m.