Triple

T9638668
Position Surface form Disambiguated ID Type / Status
Subject Sandviken Municipality E233001 entity
Predicate contains P35 FINISHED
Object Sandviken E672785 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: Sandviken | Statement: [Sandviken Municipality, contains, Sandviken]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sandviken
Context triple: [Sandviken Municipality, contains, Sandviken]
  • A. Sandviken chosen
    Sandviken is an industrial town in central Sweden, best known as the historic home of the steel company Sandvik.
  • B. Söderort
    Söderort is the southern suburban part of Stockholm, Sweden, consisting mainly of residential districts located south of the inner-city island of Södermalm.
  • C. Fredrikshamn
    Fredrikshamn (Hamina) is a coastal town in southeastern Finland that historically served as an important military and trading center.
  • D. Hjulsta
    Hjulsta is a suburb in northwestern Stockholm, Sweden, known for being the terminus of one of the Stockholm metro lines.
  • E. Strömstad
    Strömstad is a coastal town and municipality in western Sweden, near the Norwegian border, known for its archipelago, tourism, and ferry connections.
  • 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_69ca848a5a908190aad251f4137b0c3a completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9b51b08081908e30744607b28953 completed April 1, 2026, 10:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69d189fd53fc8190bc36f2b8e0e21036 completed April 4, 2026, 10 p.m.
Created at: March 30, 2026, 8:11 p.m.