Triple
T18087617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farnborough Airport |
E432877
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | EGLF |
—
|
NE NERFINISHED |
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: EGLF | Statement: [Farnborough Airport, ICAO code, EGLF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EGLF Context triple: [Farnborough Airport, ICAO code, EGLF]
-
A.
EGLF
chosen
EGLF is the ICAO airport code for Farnborough Airport, a major business aviation hub in Hampshire, England.
-
B.
EGL
EGL is the station code used to identify Eglinton station in transit systems and related services.
-
C.
EGL
EGL is an interface between Khronos rendering APIs like OpenGL ES and the native windowing system, enabling efficient rendering and context management on a variety of platforms.
-
D.
GLF
GLF is the National Rail station code for Glenfinnan railway station on the West Highland Line in the Scottish Highlands.
-
E.
GLF6
GLF6 is the ICAO aircraft type designator for the Gulfstream G600, a long-range, large-cabin business jet.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd16234c8190b547e893a829d6c5 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 10:27 a.m.