Triple

T18275456
Position Surface form Disambiguated ID Type / Status
Subject Landvetter Airport E437722 entity
Predicate namedAfter P63 FINISHED
Object Landvetter 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: Landvetter | Statement: [Landvetter Airport, namedAfter, Landvetter]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Landvetter
Context triple: [Landvetter Airport, namedAfter, Landvetter]
  • A. Landvetter chosen
    Landvetter is a locality in western Sweden that serves as a key transport hub for the Gothenburg region, best known for hosting Gothenburg Landvetter Airport.
  • B. Storvreten
    Storvreten is a residential locality within Botkyrka Municipality in the Stockholm County area of Sweden.
  • C. Utvær
    Utvær is Norway’s westernmost inhabited archipelago, known for its historic lighthouse and rugged coastal landscape in Vestland county.
  • D. Tovere
    Tovere is a small locality or hamlet that forms part of the municipality of Moltrasio in northern Italy’s Lake Como area.
  • E. Vättis
    Vättis is a village in the Swiss canton of St. Gallen, known for its alpine setting near the Tamina valley and its association with the municipality of Pfäfers.
  • 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_69d8b914530c8190b4474d862a2b2a1b completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50051bccc8190832eacdb6945d6b7 completed April 19, 2026, 4:18 p.m.
Created at: April 10, 2026, 10:34 a.m.