Triple
T6826270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gran Canaria Airport |
E157022
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | LPA |
E157022
|
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: LPA | Statement: [Gran Canaria Airport, IATA code, LPA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LPA Context triple: [Gran Canaria Airport, IATA code, LPA]
-
A.
LPA
chosen
LPA is the IATA airport code for Gran Canaria Airport, the main international gateway to Spain’s Canary Island of Gran Canaria.
-
B.
LPA
LPA is the commonly used abbreviation for the Liberal Party of Australia, a major centre-right political party in Australian federal and state politics.
-
C.
LPAZ
LPAZ is the ICAO code for Santa Maria Airport, a civil aviation facility on Santa Maria Island in Portugal’s Azores archipelago.
-
D.
LEPA
LEPA is the ICAO airport code for Palma de Mallorca Airport, a major international airport in Spain’s Balearic Islands.
-
E.
LAP
LAP is the ICAO airline designator used to identify LATAM Airlines Paraguay in international aviation operations.
- 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d58375248190935dd38d618994e3 |
completed | March 27, 2026, 7:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c723f12a148190adbb05782a2041b6 |
completed | March 28, 2026, 12:42 a.m. |
Created at: March 27, 2026, 2:18 p.m.