Triple

T4741892
Position Surface form Disambiguated ID Type / Status
Subject Drammen E105261 entity
Predicate hasTwinTown P919 FINISHED
Object Sundsvall E236744 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: Sundsvall | Statement: [Drammen, hasTwinTown, Sundsvall]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sundsvall
Context triple: [Drammen, hasTwinTown, Sundsvall]
  • A. Sundsvall chosen
    Sundsvall is a coastal city in central Sweden known as an important industrial and commercial center on the Gulf of Bothnia.
  • B. Örebro
    Örebro is a historic city in central Sweden known for its medieval castle, university, and role as a regional economic and cultural hub.
  • C. Nyköping
    Nyköping is a historic coastal town in southeastern Sweden known for its medieval castle, harbor, and role as a regional administrative and cultural center.
  • D. Skövde
    Skövde is a town in south-central Sweden that serves as a major military hub and training center for the Swedish Army.
  • E. Karlstad
    Karlstad is a city in central Sweden known as the capital of Värmland County, situated on the northern shore of Lake Vänern.
  • 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_69bd43ef87a48190a5bc3600711aa032 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64a7153881909eac451fc7566d25 completed March 20, 2026, 3:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69bfba1e755081909649e0dd8c4d2270 completed March 22, 2026, 9:45 a.m.
Created at: March 20, 2026, 1:19 p.m.