Triple

T19725443
Position Surface form Disambiguated ID Type / Status
Subject Rygge municipality E473714 entity
Predicate contains P35 FINISHED
Object Rygge Airport 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: Rygge Airport | Statement: [Rygge municipality, contains, Rygge Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rygge Airport
Context triple: [Rygge municipality, contains, Rygge Airport]
  • A. Rygge Airport chosen
    Rygge Airport is a former civil and military airport in Rygge, near Moss in southeastern Norway, which once served as a low-cost hub before closing to regular commercial traffic.
  • B. Evenes Airport
    Evenes Airport is a regional airport in northern Norway that serves as a key hub for domestic flights and access to the Lofoten and Vesterålen archipelagos.
  • C. Torp Airport
    Torp Airport is a regional international airport in Sandefjord, Norway, serving the Oslo area with both domestic and European flights.
  • D. Geiteryggen Airport
    Geiteryggen Airport is a small regional airport serving the city of Skien in Norway.
  • E. Berlevåg Airport
    Berlevåg Airport is a small regional airport in Berlevåg, Norway, primarily serving local communities with short-haul domestic flights along the northern coast.
  • 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_69d8e517ebd48190979ee76723bcfadf completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e649f7bedc81908f784832c0fc10a1 completed April 20, 2026, 3:44 p.m.
Created at: April 10, 2026, 1:46 p.m.