Triple

T18859326
Position Surface form Disambiguated ID Type / Status
Subject Drammensfjord E461266 entity
Predicate hasCityOnShore P969 FINISHED
Object Svelvik 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: Svelvik | Statement: [Drammensfjord, hasCityOnShore, Svelvik]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Svelvik
Context triple: [Drammensfjord, hasCityOnShore, Svelvik]
  • A. Svelvik chosen
    Svelvik is a small coastal town and former municipality in Vestfold og Telemark county, Norway, situated along the Drammensfjord.
  • B. Norheimsund
    Norheimsund is a village in western Norway known as a regional center in the Hardanger region, noted for its scenic fjordside setting and proximity to the Steinsdalsfossen waterfall.
  • C. Honningsvåg
    Honningsvåg is a small Arctic port town in northern Norway, often used as a gateway to the North Cape and a popular stop for cruise and coastal voyages.
  • D. Skarsvåg
    Skarsvåg is a small fishing village in northern Norway often noted as one of the world’s northernmost permanently inhabited settlements.
  • E. Gressvik
    Gressvik is a village in Fredrikstad Municipality in Viken county, Norway, located on the western side of the Glomma River.
  • 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_69d8dcfb7b9c8190854e7b171b98ea2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c05fb800819098951ec134a1fa2a completed April 20, 2026, 5:57 a.m.
Created at: April 10, 2026, 11:57 a.m.