Triple
T7129349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elko Regional Airport |
E166145
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | EKO |
E644344
|
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: EKO | Statement: [Elko Regional Airport, FAAcode, EKO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EKO Context triple: [Elko Regional Airport, FAAcode, EKO]
-
A.
EKO
chosen
EKO is the three-letter IATA airport code for Elko Regional Airport, a public airport serving Elko, Nevada, in the United States.
-
B.
OEK
OEK is the commonly used abbreviation for the Palau National Congress, the bicameral legislative body of the Republic of Palau.
-
C.
EYKA
EYKA is the ICAO airport code for Kaunas Airport, an international airport serving the city of Kaunas in Lithuania.
-
D.
Ecolo
Ecolo is a Belgian French- and German-speaking green political party known for its focus on environmentalism, social justice, and progressive policies.
-
E.
EKKA
EKKA was a Greek World War II resistance organization that played a significant role in the anti-Axis struggle and post-liberation political developments.
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e66c87848190b0ffd08e3c3f4877 |
completed | March 27, 2026, 8:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7ad8d00848190a5a4b9b64b3426e7 |
completed | March 28, 2026, 10:29 a.m. |
Created at: March 27, 2026, 2:44 p.m.