Triple
T15796559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Paso International Airport |
E382997
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | ELP |
E382996
|
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: ELP | Statement: [El Paso International Airport, hasIATACode, ELP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ELP Context triple: [El Paso International Airport, hasIATACode, ELP]
-
A.
ELP
chosen
ELP is the three-letter IATA airport code for El Paso International Airport, a commercial airport serving El Paso, Texas.
-
B.
ELPA
ELPA (Emacs Lisp Package Archive) is a primary repository and distribution system for Emacs Lisp packages used to extend and customize the Emacs editor.
-
C.
ELC
ELC is the regional vehicle registration code assigned to the area that includes the village of Walewice in Poland.
-
D.
ELM
ELM is the commonly used abbreviation for the Estonian Literary Museum, a national research and memory institution dedicated to preserving and studying Estonia’s literary and folkloric heritage.
-
E.
ELM
ELM is the three-letter IATA airport code for Elmira/Corning Regional Airport in New York, United States.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4dd4fd88190a77b224b4dee6541 |
completed | April 16, 2026, 10:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff90aea81c8190ad8bc0cdedf4b77a |
completed | May 9, 2026, 7:53 p.m. |
Created at: April 10, 2026, 4:48 a.m.