Triple

T4990568
Position Surface form Disambiguated ID Type / Status
Subject Tønsberg E112118 entity
Predicate hasNearbyIsland P970 FINISHED
Object Tjøme E190849 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: Tjøme | Statement: [Tønsberg, hasNearbyIsland, Tjøme]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tjøme
Context triple: [Tønsberg, hasNearbyIsland, Tjøme]
  • A. Tjøme chosen
    Tjøme is a scenic island and former municipality in Vestfold, Norway, known for its coastal landscapes, summer cabins, and popular seaside recreation areas.
  • B. Strømsø
    Strømsø is a historic district and former separate town that now forms part of the city of Drammen in Norway.
  • C. Drøbak
    Drøbak is a coastal town in southeastern Norway known for its historic harbor, charming wooden houses, and role as a gateway to the Oslofjord.
  • D. Sørkjosen
    Sørkjosen is a small coastal village in Northern Norway known as a gateway to the Reisa valley and Reisa National Park.
  • E. Fetsund
    Fetsund is a village in Lillestrøm Municipality in Viken county, Norway, known for its riverside location and historic timber floating facilities along the Glomma River.
  • 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_69bd441be7bc8190b530362d427b97d2 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd728141d48190a0713e6d33c50fb6 completed March 20, 2026, 4:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69beb0e1132881908fd6a540551e6318 completed March 21, 2026, 2:53 p.m.
Created at: March 20, 2026, 1:34 p.m.