Triple

T13118705
Position Surface form Disambiguated ID Type / Status
Subject Vadsø Airport E311666 entity
Predicate hasScheduledServiceTo P6787 FINISHED
Object Tromsø Airport E260491 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: Tromsø Airport | Statement: [Vadsø Airport, hasScheduledServiceTo, Tromsø Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tromsø Airport
Context triple: [Vadsø Airport, hasScheduledServiceTo, Tromsø Airport]
  • A. Bodø Airport
    Bodø Airport is a regional airport in Bodø, Norway, serving as an important hub for civilian flights and military aviation in the Nordland region.
  • B. Tromsø Airport, Langnes chosen
    Tromsø Airport, Langnes is a major regional and international airport in northern Norway serving the city of Tromsø and the surrounding Arctic region.
  • C. Bardufoss Airport
    Bardufoss Airport is a regional airport in northern Norway that serves the town of Bardufoss and the surrounding Troms area, handling both civilian and military air traffic.
  • D. Ørland Airport
    Ørland Airport is a joint civilian and military airport in Trøndelag county, Norway, serving the Ørland peninsula and surrounding Fosen region.
  • E. Røros Airport
    Røros Airport is a small regional airport in Røros, Norway, serving the local community and surrounding areas with domestic flights.
  • 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_69d806a9fe888190b081e2d9ea665d6c completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98182011c8190a504678affbb7787 completed April 10, 2026, 11:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6e284c3c881909d65e2ba89fbe7af completed May 3, 2026, 5:52 a.m.
Created at: April 9, 2026, 9:06 p.m.