Triple
T10957863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Midlands Airport |
E258891
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | EGNX |
E258892
|
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: EGNX | Statement: [East Midlands Airport, ICAO code, EGNX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EGNX Context triple: [East Midlands Airport, ICAO code, EGNX]
-
A.
EGNX
chosen
EGNX is the ICAO airport code for East Midlands Airport, a major passenger and cargo hub in central England.
-
B.
EGIS
EGIS is the principal intelligence agency of Egypt, responsible for national security, foreign intelligence, and counterintelligence operations.
-
C.
EGXH
EGXH is the ICAO airport code for RAF Honington, a Royal Air Force station in Suffolk, England.
-
D.
NX Drafting
NX Drafting is the Siemens NX module dedicated to creating, editing, and managing 2D engineering drawings from 3D CAD models.
-
E.
EGXC
EGXC is the ICAO airport code for RAF Coningsby, a major Royal Air Force station in Lincolnshire, England known for operating frontline fighter aircraft and the Battle of Britain Memorial Flight.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77126d9288190aa5daf2ba83d731d |
completed | April 9, 2026, 9:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e2d751e8e081908f31ab2d82105c3c |
completed | April 18, 2026, 12:58 a.m. |
Created at: April 8, 2026, 9:23 p.m.