Triple

T11939442
Position Surface form Disambiguated ID Type / Status
Subject Rovaniemi Airport E284135 entity
Predicate operator P179 FINISHED
Object Finavia E412708 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: Finavia | Statement: [Rovaniemi Airport, operator, Finavia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Finavia
Context triple: [Rovaniemi Airport, operator, 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. Lappeenranta Airport
    Lappeenranta Airport is a regional airport in southeastern Finland that serves the city of Lappeenranta and provides both domestic and international flight connections.
  • 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_69d6ab2ce9c48190b5d39511b524f666 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903415d2481909d84e6727454b9fe completed April 10, 2026, 2:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69f4409a40dc81909d87c50601b98b78 completed May 1, 2026, 5:56 a.m.
Created at: April 8, 2026, 9:45 p.m.