Triple
T9381138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow Airport |
E225785
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | GLA |
E225784
|
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: GLA | Statement: [Glasgow Airport, IATACode, GLA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GLA Context triple: [Glasgow Airport, IATACode, GLA]
-
A.
GLA
chosen
GLA is the three-letter IATA airport code for Glasgow Airport, the main international airport serving Glasgow, Scotland.
-
B.
Gla
Gla is a large fortified Mycenaean archaeological site in Boeotia, Greece, notable for its massive walls and strategic position overlooking the former Lake Kopais.
-
C.
GCLA
GCLA is the ICAO airport code for La Palma Airport in Spain’s Canary Islands.
-
D.
GLAA
GLAA is a UK government body responsible for licensing labour providers and investigating labour exploitation and modern slavery in high-risk sectors.
-
E.
Agly
The Agly is a river in southern France that flows through the Occitanie region before emptying into the Mediterranean Sea.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50be52248190bc7cd9deb95a1ef8 |
completed | April 1, 2026, 5:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d100ddec0c8190854fb5db36e840db |
completed | April 4, 2026, 12:15 p.m. |
Created at: March 30, 2026, 7:44 p.m.