Triple

T19738912
Position Surface form Disambiguated ID Type / Status
Subject North Denmark Region E474059 entity
Predicate hasIsland P970 FINISHED
Object Læsø 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: Læsø | Statement: [North Denmark Region, hasIsland, Læsø]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Læsø
Context triple: [North Denmark Region, hasIsland, Læsø]
  • A. Læsø chosen
    Læsø is a Danish island in the Kattegat known for its salt production, distinctive seaweed-roofed houses, and tranquil coastal landscapes.
  • B. Mandø
    Mandø is a small Danish island in the Wadden Sea, known for its tidal causeway access, rich birdlife, and traditional marshland landscapes.
  • C. Hvidøen
    Hvidøen is the former name of Kvitøya, a remote, ice-covered island in the Svalbard archipelago of the Arctic Ocean.
  • D. Rømø
    Rømø is a Danish island in the Wadden Sea known for its expansive sandy beaches, coastal dunes, and popular holiday resorts.
  • E. Langeland
    Langeland is a Danish island in the South Funen Archipelago, known for its rural landscapes, coastal scenery, and historical villages.
  • 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_69e6515f6efc8190a3da113847464399 completed April 20, 2026, 4:16 p.m.
Created at: April 10, 2026, 1:47 p.m.