Triple
T9150007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porter County Regional Airport |
E219560
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | VPZ |
E781286
|
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: VPZ | Statement: [Porter County Regional Airport, FAAcode, VPZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VPZ Context triple: [Porter County Regional Airport, FAAcode, VPZ]
-
A.
VPZ
chosen
VPZ is the IATA airport code for Porter County Regional Airport serving Valparaiso, Indiana.
-
B.
VZ
VZ is the stock ticker symbol for Verizon Communications Inc., a major U.S.-based telecommunications company providing wireless, internet, and related services.
-
C.
PZ
PZ is the vehicle registration code used on license plates for vehicles registered in the Preveza regional unit of Greece.
-
D.
PZ
PZ is the IATA airline designator assigned to LATAM Airlines Paraguay, the Paraguayan branch of the LATAM Airlines Group.
-
E.
VEVZ
VEVZ is the ICAO airport code for Visakhapatnam Airport, a major civil and military airfield serving the city of Visakhapatnam in Andhra Pradesh, India.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca96908d88190a1d12517f6d1aece |
completed | April 1, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0545c5bb48190b889e6e9ef0448a5 |
completed | April 3, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:20 p.m.