Triple
T13938178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evansville Regional Airport |
E335171
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | EVV |
E1070912
|
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: EVV | Statement: [Evansville Regional Airport, FAA LID, EVV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EVV Context triple: [Evansville Regional Airport, FAA LID, EVV]
-
A.
EVV
chosen
EVV is the three-letter IATA airport code for Evansville Regional Airport in Evansville, Indiana.
-
B.
EVB
EVB (Edge Virtual Bridging) is an IEEE networking standard that defines mechanisms for managing and integrating virtualized network interfaces on edge switches and servers in data center environments.
-
C.
ECV
ECV is the IATA airport code for Cuatro Vientos Air Base, a historic military and general aviation airfield near Madrid, Spain.
-
D.
ESSV
ESSV is the ICAO airport code for Visby Airport, the main airport serving the island of Gotland in Sweden.
-
E.
EVS
EVS (Enhanced Voice Services) is a modern audio codec designed to deliver high-quality, low-latency voice and audio over LTE and other IP-based communication networks.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf5cc8c8190bea74291702b2925 |
completed | April 14, 2026, 12:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fba1c81e988190a5fd8e2d83e065fe |
completed | May 6, 2026, 8:17 p.m. |
Created at: April 9, 2026, 10:17 p.m.