Triple

T16542417
Position Surface form Disambiguated ID Type / Status
Subject EPLL E401851 entity
Predicate formerName P65 FINISHED
Object Łódź-Lublinek Airport E92171 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: Łódź-Lublinek Airport | Statement: [EPLL, formerName, Łódź-Lublinek Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Łódź-Lublinek Airport
Context triple: [EPLL, formerName, Łódź-Lublinek Airport]
  • A. Łódź Władysław Reymont Airport chosen
    Łódź Władysław Reymont Airport is a regional international airport in central Poland serving the city of Łódź and its surrounding area.
  • B. Lublin Airport
    Lublin Airport is a regional international airport in eastern Poland serving the city of Lublin and its surrounding area.
  • C. Poznań–Ławica Airport
    Poznań–Ławica Airport is an international airport in western Poland serving the city of Poznań with domestic and European flights.
  • D. Radom-Sadków Airport
    Radom-Sadków Airport is a regional civil-military airport in Radom, Poland, serving domestic and limited international flights.
  • E. Warsaw Modlin Airport
    Warsaw Modlin Airport is a secondary international airport serving the Warsaw metropolitan area, primarily used by low-cost carriers and located northwest of the city.
  • 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_69d88384bc30819084229e7dcdc39a41 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3455db6788190b929546050ea2488 completed April 18, 2026, 8:48 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0091891c5081908f37598a17417c94 completed May 10, 2026, 2:09 p.m.
Created at: April 10, 2026, 5:15 a.m.