Triple

T10374162
Position Surface form Disambiguated ID Type / Status
Subject Rygge E244459 entity
Predicate hasNotableFacility P105 FINISHED
Object Moss Airport, Rygge E439027 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: Moss Airport, Rygge | Statement: [Rygge, hasNotableFacility, Moss Airport, Rygge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moss Airport, Rygge
Context triple: [Rygge, hasNotableFacility, Moss Airport, Rygge]
  • A. Moss Airport, Rygge chosen
    Moss Airport, Rygge was a former civil and military airport in southeastern Norway that served the Oslo region with both commercial and charter flights.
  • B. 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.
  • C. 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.
  • 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. Leknes Airport
    Leknes Airport is a small regional airport in Norway’s Lofoten archipelago that provides vital domestic connections for residents and tourists.
  • 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_69d381b3e328819094b23b8edcd29b5a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e9804e708190b15f5d38cac9c4c1 completed April 7, 2026, 11:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69d7fb98c52c8190a52682feacc2bd0d completed April 9, 2026, 7:18 p.m.
Created at: April 6, 2026, 12:02 p.m.