Triple

T18632604
Position Surface form Disambiguated ID Type / Status
Subject Central Sweden E455459 entity
Predicate hasMajorCity P316 FINISHED
Object Borlänge 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: Borlänge | Statement: [Central Sweden, hasMajorCity, Borlänge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Borlänge
Context triple: [Central Sweden, hasMajorCity, Borlänge]
  • A. Borlänge chosen
    Borlänge is an industrial town in central Sweden’s Dalarna County, known for its steel production, logistics hub, and role as a regional commercial center.
  • B. Bollnäs
    Bollnäs is a small Swedish town known for its scenic lakeside setting, traditional wooden architecture, and strong bandy sports culture.
  • C. Ljungan
    Ljungan is a river in central Sweden that flows through Jämtland and Västernorrland counties before emptying into the Gulf of Bothnia.
  • D. Österlen
    Österlen is a picturesque rural area in southeastern Skåne, Sweden, known for its rolling farmland, coastal landscapes, and vibrant arts and tourism scene.
  • E. Bollstanäs
    Bollstanäs is a residential locality in Sweden situated within the suburban area of Upplands Väsby, north of Stockholm.
  • 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_69d8d38cc7948190a55ea64e5638994e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54fc5c7ec8190ab0c64f009583f96 completed April 19, 2026, 9:57 p.m.
Created at: April 10, 2026, 11:46 a.m.