Triple
T5116999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid-Ohio Valley Regional Airport |
E115360
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | PKB |
E495348
|
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: PKB | Statement: [Mid-Ohio Valley Regional Airport, FAA LID, PKB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PKB Context triple: [Mid-Ohio Valley Regional Airport, FAA LID, 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.
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.
-
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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd77ccb19c8190844c628ff7cfcca2 |
completed | March 20, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69becfcf12448190a196e9397958fbba |
completed | March 21, 2026, 5:05 p.m. |
Created at: March 20, 2026, 1:41 p.m.