Triple

T19033730
Position Surface form Disambiguated ID Type / Status
Subject Vilnius Airport E465809 entity
Predicate hasNativeName P1435 FINISHED
Object Vilniaus oro uostas 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: Vilniaus oro uostas | Statement: [Vilnius Airport, hasNativeName, Vilniaus oro uostas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vilniaus oro uostas
Context triple: [Vilnius Airport, hasNativeName, Vilniaus oro uostas]
  • A. Vilnius Airport chosen
    Vilnius Airport is the main international airport serving Lithuania’s capital, handling the majority of the region’s passenger and air traffic.
  • B. Kaunas Airport
    Kaunas Airport is an international airport in Lithuania serving the city of Kaunas and functioning as one of the country’s main commercial and low-cost airline hubs.
  • C. Palanga Airport
    Palanga Airport is a regional international airport in western Lithuania serving the coastal resort city of Palanga and the surrounding Baltic Sea region.
  • D. Zarasai
    Zarasai is a small town in northeastern Lithuania known for its lakes and scenic natural surroundings.
  • E. Vilnius railway station
    Vilnius railway station is the main passenger and freight rail hub of Lithuania’s capital, serving as a key national and international transport gateway.
  • 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_69d8dd0359648190bc2a9202c5cf29d2 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d741cabc8190900e12265ad269f8 completed April 20, 2026, 7:35 a.m.
Created at: April 10, 2026, 12:02 p.m.