Triple

T21321952
Position Surface form Disambiguated ID Type / Status
Subject Sandvig Beach E525639 entity
Predicate locatedIn P40 FINISHED
Object Sandvig 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: Sandvig | Statement: [Sandvig Beach, locatedIn, Sandvig]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sandvig
Context triple: [Sandvig Beach, locatedIn, Sandvig]
  • A. Sandvig chosen
    Sandvig is a coastal village on the northern tip of the Danish island of Bornholm, known for its scenic rocky shoreline and role as part of the twin town Allinge-Sandvig.
  • B. Møvig
    Møvig is a coastal area in Kristiansand, Norway, known for its maritime setting and historical World War II coastal fortifications.
  • C. Delvig
    Delvig is a surname most notably associated with Anton Delvig, a Russian poet and contemporary of Alexander Pushkin.
  • D. Vigerslev
    Vigerslev is a neighborhood within the Valby district of Copenhagen, Denmark, known primarily as a residential area with local amenities and transport links.
  • E. Svaneke
    Svaneke is a picturesque coastal town on the Danish island of Bornholm, known for its well-preserved half-timbered houses, harbor, and traditional smokehouses.
  • 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_69e0b51ad810819098c12392c8e55f6c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e77ed2640c8190a81b087e2c49c500 completed April 21, 2026, 1:42 p.m.
Created at: April 16, 2026, 4:40 p.m.