Triple
T17970132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverness Airport |
E449313
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | EGPE |
—
|
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: EGPE | Statement: [Inverness Airport, ICAOcode, EGPE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EGPE Context triple: [Inverness Airport, ICAOcode, EGPE]
-
A.
EGPE
chosen
EGPE is the ICAO airport code for Inverness Airport, a regional airport serving the city of Inverness and the Scottish Highlands.
-
B.
EPGP
EPGP is a postgraduate management program designed for experienced professionals, typically offered in an executive or part-time format to enhance managerial and leadership skills.
-
C.
EGPK
EGPK is the ICAO airport code for Glasgow Prestwick Airport, an international airport serving the Ayrshire region of Scotland.
-
D.
EGPF
EGPF is the ICAO airport code for Glasgow Airport, a major international airport serving the Greater Glasgow area in Scotland.
-
E.
EGE
EGE is the IATA airport code for Eagle County Regional Airport, a commercial airport serving the Vail and Eagle Valley region in Colorado, USA.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b13b1b088190b7d71006b31e5cc3 |
completed | April 19, 2026, 10:40 a.m. |
Created at: April 10, 2026, 10:22 a.m.