Triple

T23318137
Position Surface form Disambiguated ID Type / Status
Subject Vaxholmen E590767 entity
Predicate locatedNear P294 FINISHED
Object Vaxön 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: Vaxön | Statement: [Vaxholmen, locatedNear, Vaxön]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vaxön
Context triple: [Vaxholmen, locatedNear, Vaxön]
  • A. Vaxön chosen
    Vaxön is a central island in Sweden’s Stockholm archipelago that forms the core of the town of Vaxholm and serves as an important hub for local ferry and coastal traffic.
  • B. Vasön
    Vasön is a small village in the municipality of Pfäfers in the canton of St. Gallen, Switzerland, known for its scenic Alpine setting.
  • C. Västerljung
    Västerljung is a small locality in eastern Sweden situated within Trosa Municipality in Södermanland County.
  • D. Vágar
    Vágar is one of the main islands of the Faroe Islands, known for hosting the archipelago’s only airport and serving as a key transport hub.
  • E. Frövi
    Frövi is a small locality in central Sweden known historically as a railway junction and industrial community.
  • 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_69e25d1d32188190948eb76909d1dcc3 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1978372948190bad066893c4e0768 completed April 29, 2026, 5:30 a.m.
Created at: April 17, 2026, 5:07 p.m.