Triple

T3441724
Position Surface form Disambiguated ID Type / Status
Subject Dalarna E72579 entity
Predicate borders P224 FINISHED
Object Hälsingland E238313 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: Hälsingland | Statement: [Dalarna, borders, Hälsingland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hälsingland
Context triple: [Dalarna, borders, Hälsingland]
  • A. Hälsingland chosen
    Hälsingland is a historical province in central Sweden known for its traditional decorated farmhouses, forests, and cultural heritage.
  • B. Uppland
    Uppland is a historical province in east-central Sweden that includes parts of the greater Stockholm area and key infrastructure such as Stockholm Arlanda Airport.
  • C. Bohuslän
    Bohuslän is a coastal province in western Sweden known for its rugged granite shoreline, fishing villages, and archipelago along the Skagerrak.
  • D. Dalsland
    Dalsland is a historical province in western Sweden known for its forests, lakes, and rural landscapes.
  • E. Svealand
    Svealand is the central region of Sweden, historically significant as the country's core area and home to the capital city, Stockholm.
  • 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_69ad85af50288190a854b76653deee6f completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adba276b708190949f294a8d09ec7b completed March 8, 2026, 6:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69b360d0beb08190921d7cfe6b86eab2 completed March 13, 2026, 12:56 a.m.
Created at: March 8, 2026, 3:16 p.m.