Triple

T4098457
Position Surface form Disambiguated ID Type / Status
Subject Helsinki Airport E87879 entity
Predicate ownedBy P347 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: [Helsinki Airport, ownedBy, Finavia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Finavia
Context triple: [Helsinki 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. Tampere–Pirkkala Airport
    Tampere–Pirkkala Airport is a Finnish international airport serving the Tampere region, handling both civilian air traffic and military operations.
  • D. 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.
  • E. Jyväskylä Airport
    Jyväskylä Airport is a regional airport in central Finland that serves the city of Jyväskylä with domestic flights and general aviation services.
  • 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_69aed94564cc8190a9c1457daedb6e7f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefce017708190a4d33753fd32a7bb completed March 9, 2026, 5:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69b576a1a0408190aa4683a0904790aa completed March 14, 2026, 2:54 p.m.
Created at: March 9, 2026, 3:40 p.m.