Triple

T21308367
Position Surface form Disambiguated ID Type / Status
Subject Kiruna Airport E525261 entity
Predicate serves P98 FINISHED
Object Kiruna 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: Kiruna | Statement: [Kiruna Airport, serves, Kiruna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kiruna
Context triple: [Kiruna Airport, serves, Kiruna]
  • A. Kiruna chosen
    Kiruna is a mining town in northern Sweden known for its large iron ore mine and its location above the Arctic Circle.
  • B. Gällivare
    Gällivare is a mining town in northern Sweden known for its significant iron ore deposits and role in the region’s mining industry.
  • C. Narvik
    Narvik is a port town in northern Norway known for its strategic importance during World War II and as the site of major naval and land battles.
  • D. Pajala
    Pajala is a small town in northern Sweden’s Lapland region, known for its remote Arctic setting and as the backdrop of several works by author Mikael Niemi.
  • E. Haparanda
    Haparanda is a small Swedish town on the border with Finland, known as a key cross-border trading hub and the easternmost town in Sweden.
  • 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_69e0b518b8948190ad69cf9a8784d397 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e75aa863688190a5e45248e31eec88 completed April 21, 2026, 11:08 a.m.
Created at: April 16, 2026, 4:06 p.m.