Triple

T22133412
Position Surface form Disambiguated ID Type / Status
Subject Oulu Airport E546963 entity
Predicate ownedBy P347 FINISHED
Object Finavia 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: Finavia | Statement: [Oulu Airport, ownedBy, Finavia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Finavia
Context triple: [Oulu Airport, ownedBy, Finavia]
  • A. Finavia chosen
    Finavia is the Finnish state-owned company responsible for operating and maintaining Finland’s network of airports and air navigation services.
  • B. Helsinki Airport
    Helsinki Airport is Finland’s main international air hub, located near Helsinki and serving as a major gateway between Europe and Asia.
  • C. Turku Airport
    Turku Airport is an international airport in southwestern Finland serving the city of Turku and the surrounding region with passenger and cargo flights.
  • D. Tampere–Pirkkala Airport
    Tampere–Pirkkala Airport is a Finnish international airport serving the Tampere region, handling both civilian air traffic and military operations.
  • E. Savonlinna Airport
    Savonlinna Airport is a small regional airport in Savonlinna, Finland, providing domestic air connections for the surrounding South Savo area.
  • 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_69e11e39bf348190b541bfa16a7b71e0 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129b81d5c819085fd18bf3ae28333 completed April 28, 2026, 9:42 p.m.
Created at: April 16, 2026, 8:32 p.m.