Triple

T20824064
Position Surface form Disambiguated ID Type / Status
Subject Baltic Sea islands E512649 entity
Predicate includes P1393 FINISHED
Object Sandhamn 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: Sandhamn | Statement: [Baltic Sea islands, includes, Sandhamn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sandhamn
Context triple: [Baltic Sea islands, includes, Sandhamn]
  • A. Sandhamn chosen
    Sandhamn is a popular Swedish island village and sailing hub in the outer Stockholm archipelago, known for its beaches, regattas, and picturesque wooden houses.
  • B. Sandholmen
    Sandholmen is an island within Finland’s Pellinge archipelago, known for its coastal nature and maritime surroundings.
  • C. Särna
    Särna is a small locality in northern Dalarna County, Sweden, known for its forested surroundings and outdoor recreation opportunities.
  • D. Skärhamn
    Skärhamn is a coastal town in western Sweden known for its fishing heritage, picturesque harbor, and the Nordic Watercolour Museum.
  • E. Græsholm
    Græsholm is a small Danish island that forms part of the Hirsholmene archipelago in the Kattegat.
  • 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_69e0b4ce39108190a6e8e5df4f1c8dc5 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2fc0cd081909e264cda686579ea completed April 21, 2026, 12:21 a.m.
Created at: April 16, 2026, 12:41 p.m.