Triple

T20628774
Position Surface form Disambiguated ID Type / Status
Subject Högalid Church E506891 entity
Predicate locatedIn P40 FINISHED
Object Högalid 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: Högalid | Statement: [Högalid Church, locatedIn, Högalid]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Högalid
Context triple: [Högalid Church, locatedIn, Högalid]
  • A. Högalid chosen
    Högalid is a district in the Södermalm area of central Stockholm, Sweden, known for its elevated location and the prominent Högalid Church that overlooks the city.
  • B. Hjorthagen
    Hjorthagen is a residential district in northeastern Stockholm, Sweden, known for its mix of historic workers’ housing and modern developments near the Royal National City Park and the Värtan harbor area.
  • C. Hornodden
    Hornodden is a remote Arctic headland located on the island of Kvitøya in the Svalbard archipelago of Norway.
  • D. Hunoldstal
    Hunoldstal is a small district or locality within the municipality of Schmitten in the Hochtaunus region of Hesse, Germany.
  • E. Hurdal
    Hurdal is a rural municipality in Viken county, Norway, known for its forests, lakes, and outdoor recreation areas such as Hurdalssjøen.
  • 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_69e0b4bd4a0081908d4e97a590a33fb2 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6abe771e88190a48471bf83b4804d completed April 20, 2026, 10:42 p.m.
Created at: April 16, 2026, 11:42 a.m.