Triple

T23351732
Position Surface form Disambiguated ID Type / Status
Subject Skarnsund Bridge E592930 entity
Predicate locatedNear P294 FINISHED
Object Vangshylla 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: Vangshylla | Statement: [Skarnsund Bridge, locatedNear, Vangshylla]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vangshylla
Context triple: [Skarnsund Bridge, locatedNear, Vangshylla]
  • A. Vangshylla chosen
    Vangshylla is a small coastal settlement in Trøndelag county, Norway, known for its location along the Beitstadfjorden and its fishing and boating activities.
  • B. Bergshamra
    Bergshamra is a residential district in the northern Stockholm urban area of Sweden, known for its proximity to green spaces and good public transport connections.
  • C. Kvernberget
    Kvernberget is a hill and surrounding area in Kristiansund, Norway, known for giving its name to the nearby regional airport.
  • D. Stöllet
    Stöllet is a small locality in central Sweden situated within Torsby Municipality in Värmland County.
  • E. Storvreten
    Storvreten is a residential locality within Botkyrka Municipality in the Stockholm County area of Sweden.
  • 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_69e25d24d2a4819092e6ede74c2a918d completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f19a1401748190b77df0a45c2aeebf completed April 29, 2026, 5:41 a.m.
Created at: April 17, 2026, 5:20 p.m.