Triple

T13147006
Position Surface form Disambiguated ID Type / Status
Subject Leknes Airport E312365 entity
Predicate serves P98 FINISHED
Object Leknes E312365 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: Leknes | Statement: [Leknes Airport, serves, Leknes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leknes
Context triple: [Leknes Airport, serves, Leknes]
  • A. Leknes chosen
    Leknes is a small coastal town in Norway’s Lofoten archipelago, known for its dramatic mountain-and-sea landscapes and role as a regional commercial center.
  • B. Alstahaug
    Alstahaug is a coastal municipality in northern Norway known for its historic church, island landscapes, and maritime heritage.
  • C. Naustdal
    Naustdal is a small coastal village and former municipality in Vestland county, western Norway, known for its fjord landscape and salmon-rich Nausta River.
  • D. Hustadvika
    Hustadvika is a coastal municipality in western Norway known for its rugged shoreline and treacherous shipping waters along the Norwegian Sea.
  • E. Seltjarnarnes
    Seltjarnarnes is a small coastal municipality in the Capital Region of Iceland, located on a peninsula just west of Reykjavík.
  • 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_69d806aabde48190899e13e41659cae5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98bd0f5b08190ab700c5de1c8e138 completed April 10, 2026, 11:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6f5da0f708190b848601e571a9fff completed May 3, 2026, 7:14 a.m.
Created at: April 9, 2026, 9:10 p.m.