Triple
T6255025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Paso Locomotive FC |
E140140
|
entity |
| Predicate | usesAbbreviation |
P43
|
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 Locomotive FC, usesAbbreviation, ELP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ELP Context triple: [El Paso Locomotive FC, usesAbbreviation, 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.
ELP Communications
ELP Communications was an American television production company best known for producing popular sitcoms and other network TV series in the late 20th century.
-
E.
EFLP
EFLP is the ICAO airport code for Lappeenranta Airport in Lappeenranta, Finland.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06363d6008190bf05e003b1f74497 |
completed | March 22, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c2443138788190835ed3fd99f21827 |
completed | March 24, 2026, 7:58 a.m. |
Created at: March 22, 2026, 4:24 p.m.