Triple

T9195028
Position Surface form Disambiguated ID Type / Status
Subject Rzeszów E220683 entity
Predicate hasAirport P105 FINISHED
Object Rzeszów–Jasionka Airport E121065 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: Rzeszów–Jasionka Airport | Statement: [Rzeszów, hasAirport, Rzeszów–Jasionka Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rzeszów–Jasionka Airport
Context triple: [Rzeszów, hasAirport, Rzeszów–Jasionka Airport]
  • A. Rzeszów–Jasionka Airport chosen
    Rzeszów–Jasionka Airport is an international airport in southeastern Poland serving the city of Rzeszów and the surrounding Subcarpathian region.
  • B. Kielce-Masłów Airport
    Kielce-Masłów Airport is a small regional airport in the Świętokrzyskie Voivodeship of Poland serving the city of Kielce and surrounding areas.
  • C. Lutsk Airport
    Lutsk Airport is a regional civil and military airfield serving the city of Lutsk and the surrounding area in western Ukraine.
  • D. Katowice Airport
    Katowice Airport is an international airport in southern Poland serving the Silesian region with domestic and European flights.
  • E. Lublin Airport
    Lublin Airport is a regional international airport in eastern Poland serving the city of Lublin and its surrounding area.
  • 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_69ca83e7ba70819088b74866d9da2c30 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccd87c3a3c8190b60f19873ef6e1f8 completed April 1, 2026, 8:34 a.m.
NED1 Entity disambiguation (via context triple) batch_69d05c313004819090fe0e5d4e7bc15e completed April 4, 2026, 12:32 a.m.
Created at: March 30, 2026, 7:25 p.m.