Triple

T15021155
Position Surface form Disambiguated ID Type / Status
Subject BOO E378086 entity
Predicate appliesTo P1129 FINISHED
Object Bodø Airport E379144 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: Bodø Airport | Statement: [BOO, appliesTo, Bodø Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bodø Airport
Context triple: [BOO, appliesTo, Bodø Airport]
  • A. Bodø Airport chosen
    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. 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øst Airport
    Røst Airport is a small regional airport serving the island community of Røst in Nordland county, Norway, providing vital air connections to the mainland.
  • D. 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.
  • E. Honningsvåg Airport
    Honningsvåg Airport is a small regional airport in northern Norway that primarily serves the town of Honningsvåg and provides access to the North Cape area.
  • 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_69d85cd3a3c881908c71fc424d459c17 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded765462c819097f331c9b39c80e3 completed April 15, 2026, 12:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69fea5b0bbf4819082e14715bfd6003d completed May 9, 2026, 3:10 a.m.
Created at: April 10, 2026, 2:56 a.m.