Triple
T13260990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGXH |
E315791
|
entity |
| Predicate | hasIcaoCode |
P419
|
FINISHED |
| Object | EGXH |
E315791
|
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: EGXH | Statement: [EGXH, hasIcaoCode, EGXH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EGXH Context triple: [EGXH, hasIcaoCode, EGXH]
-
A.
EGXH
chosen
EGXH is the ICAO airport code for RAF Honington, a Royal Air Force station in Suffolk, England.
-
B.
EGXV
EGXV is the ICAO airport code for RAF Leconfield, a former Royal Air Force station in East Yorkshire, England.
-
C.
EGXW
EGXW is the ICAO airport code for RAF Waddington, a major Royal Air Force station in Lincolnshire, England.
-
D.
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.
-
E.
EGDX
EGDX is the ICAO airport code for the Royal Air Force and Ministry of Defence airfield at St Athan in South Wales, United Kingdom.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9901b380881909e6520fbb6811084 |
completed | April 11, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f716cac5388190a839ec1dbdcdbf82 |
completed | May 3, 2026, 9:35 a.m. |
Created at: April 9, 2026, 9:25 p.m.