Triple

T11360015
Position Surface form Disambiguated ID Type / Status
Subject Hörby E269060 entity
Predicate hasAdministrativeCenter P1474 FINISHED
Object Hörby (locality) E269060 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örby (locality) | Statement: [Hörby, hasAdministrativeCenter, Hörby (locality)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hörby (locality)
Context triple: [Hörby, hasAdministrativeCenter, Hörby (locality)]
  • A. Hörby chosen
    Hörby is a small municipality in southern Sweden’s Skåne County, known for its rural landscape and traditional Swedish town character.
  • B. Högsby Municipality
    Högsby Municipality is a small local government area in southeastern Sweden known for its rural landscapes, forests, and lakes.
  • C. Örbyhus
    Örbyhus is a small locality in Uppsala County, Sweden, known for its railway connections and proximity to historical sites such as Örbyhus Castle.
  • D. Vårby
    Vårby is a suburban district in the southern Stockholm area of Sweden, known for its residential neighborhoods and proximity to Lake Mälaren.
  • E. Ljungby Municipality
    Ljungby Municipality is a local government area in southern Sweden known for its forests, lakes, and the town of Ljungby as its administrative center.
  • 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_69d6aacbe18081909e5fadb50082dd96 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7ea42fe608190b9c71dd63f8780f3 completed April 9, 2026, 6:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69e543bdd6d88190b4f816ffde5179be completed April 19, 2026, 9:06 p.m.
Created at: April 8, 2026, 9:33 p.m.