Triple

T9975719
Position Surface form Disambiguated ID Type / Status
Subject Hudiksvall Municipality E196321 entity
Predicate hasDemonym P191 FINISHED
Object Hudiksvallsbo E257400 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: Hudiksvallsbo | Statement: [Hudiksvall Municipality, hasDemonym, Hudiksvallsbo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hudiksvallsbo
Context triple: [Hudiksvall Municipality, hasDemonym, Hudiksvallsbo]
  • A. Bollstanäs
    Bollstanäs is a residential locality in Sweden situated within the suburban area of Upplands Väsby, north of Stockholm.
  • B. Kungsbacka
    Kungsbacka is a town in southwestern Sweden known for its coastal location, historic wooden center, and role as a commuter hub for nearby Gothenburg.
  • C. Hudiksvall chosen
    Hudiksvall is a coastal town in east-central Sweden known for its historic wooden buildings and harbor on the Gulf of Bothnia.
  • D. Svalöv
    Svalöv is a small locality and municipality in Skåne County in southern Sweden, known for its rural landscape and agricultural surroundings.
  • E. Skarpäng
    Skarpäng is a residential urban area within Täby Municipality in Stockholm County, Sweden.
  • 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_69ca82eea2b88190a0e511d21a31f386 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb84b47308190aa2f94fa7320cdc3 completed April 2, 2026, 12:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69d23de601f0819096004bf60ffa2d2c completed April 5, 2026, 10:48 a.m.
Created at: March 30, 2026, 8:48 p.m.