Triple

T10661380
Position Surface form Disambiguated ID Type / Status
Subject Aalborg Airport E251232 entity
Predicate locatedNear P294 FINISHED
Object Limfjord E176948 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: Limfjord | Statement: [Aalborg Airport, locatedNear, Limfjord]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Limfjord
Context triple: [Aalborg Airport, locatedNear, Limfjord]
  • A. Limfjord chosen
    Limfjord is a shallow sound and strait in northern Denmark that separates the northern tip of the Jutland Peninsula from the rest of the mainland and connects the North Sea with the Kattegat.
  • B. Nissum Fjord
    Nissum Fjord is a shallow coastal lagoon on the west coast of Jutland in Denmark, known for its rich birdlife, dunes, and surrounding protected natural areas.
  • C. Mossefjord
    Mossefjord is a coastal fjord in southeastern Norway known for bordering the town of Moss and forming part of the Oslofjord system.
  • D. Aabenraa Fjord
    Aabenraa Fjord is a coastal inlet in southern Denmark known for its sheltered waters and the harbor town of Aabenraa along its shores.
  • E. Iddefjord
    Iddefjord is a narrow fjord forming part of the border between Norway and Sweden, known for its scenic landscapes and proximity to the town of Halden.
  • 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_69d6aa5b0d2881909584b20efc5877f0 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6e017f97c8190b22765a6f1e6719d completed April 8, 2026, 11:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69d97a8cabc88190b430cb08ed0fc515 completed April 10, 2026, 10:32 p.m.
Created at: April 8, 2026, 9:08 p.m.