Triple

T20369140
Position Surface form Disambiguated ID Type / Status
Subject Lappeenranta Airport E496998 entity
Predicate IATA code P2569 FINISHED
Object LPP 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: LPP | Statement: [Lappeenranta Airport, IATA code, LPP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LPP
Context triple: [Lappeenranta Airport, IATA code, LPP]
  • A. LPP chosen
    LPP is the IATA airport code for Lappeenranta Airport in Lappeenranta, Finland.
  • B. LPPS
    LPPS is the ICAO airport code for Porto Santo Airport, which serves the island of Porto Santo in Portugal’s Madeira archipelago.
  • C. LPPR
    LPPR is the ICAO airport code for Francisco Sá Carneiro Airport, the international airport serving Porto, Portugal.
  • D. LPPD
    LPPD is the ICAO airport code for João Paulo II Airport, the main international airport serving Ponta Delgada in the Azores, Portugal.
  • E. LPPT
    LPPT is the ICAO airport code for Humberto Delgado Airport, the main international airport serving Lisbon, Portugal.
  • 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_69e0b4a4f9b081908a5a021919c21ccb completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6787454a88190ae87d9b3c9b5ad27 completed April 20, 2026, 7:03 p.m.
Created at: April 16, 2026, 11:26 a.m.