Triple

T23412545
Position Surface form Disambiguated ID Type / Status
Subject Terminal 1 (Lisbon Humberto Delgado Airport) E560114 entity
Predicate IATAAirportCodeOfParent P2569 FINISHED
Object LIS 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: LIS | Statement: [Terminal 1 (Lisbon Humberto Delgado Airport), IATAAirportCodeOfParent, LIS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LIS
Context triple: [Terminal 1 (Lisbon Humberto Delgado Airport), IATAAirportCodeOfParent, LIS]
  • A. LIS chosen
    LIS is the three-letter IATA airport code for Humberto Delgado Airport, the main international airport serving Lisbon, Portugal.
  • B. LIS
    LIS is a U.S. Medicare program that helps low-income beneficiaries pay for their Medicare Part D prescription drug costs.
  • C. LISN
    LISN is the stock ticker symbol for Chocoladefabriken Lindt & Sprüngli AG, the Swiss premium chocolate manufacturer.
  • D. Lis
    Lis is a small unincorporated rural community located in Jasper County in the U.S. state of Illinois.
  • E. Lis
    Lis is a diminutive form of the given name Lisa, commonly used as a short or affectionate variant.
  • 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_69e2454b3a5881909c64773dc8a5d289 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1a5124a54819087a7ae2f8a5b3dc0 completed April 29, 2026, 6:28 a.m.
Created at: April 17, 2026, 5:38 p.m.