Triple

T6290551
Position Surface form Disambiguated ID Type / Status
Subject Vaxholm Fortress E141004 entity
Predicate locatedNear P294 FINISHED
Object Vaxholm town E498140 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: Vaxholm town | Statement: [Vaxholm Fortress, locatedNear, Vaxholm town]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vaxholm town
Context triple: [Vaxholm Fortress, locatedNear, Vaxholm town]
  • A. Vaxholm chosen
    Vaxholm is a small coastal town and municipality in the Stockholm archipelago of eastern Sweden, known for its historic fortress and picturesque waterfront.
  • B. Vaxholm Municipality
    Vaxholm Municipality is a coastal municipality in east-central Sweden known for its archipelago setting and historic fortress town of Vaxholm.
  • C. Värtahamnen
    Värtahamnen is a major port and harbor area in Stockholm, Sweden, serving as an important hub for ferry, cargo, and cruise traffic in the Baltic Sea region.
  • D. Värmdö
    Värmdö is a large island and municipality in the Stockholm archipelago of Sweden, known for its coastal landscapes, holiday homes, and proximity to Stockholm.
  • E. Storholmen
    Storholmen is an island located in Lake Femunden, one of Norway’s largest inland lakes.
  • 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_69c008cdf2ac8190bb640c94478fb4ed completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0641ca91481909d49b700cef93ffe completed March 22, 2026, 9:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69c5197f0f9c81909f5b6de50e61560c completed March 26, 2026, 11:33 a.m.
Created at: March 22, 2026, 4:26 p.m.