Triple

T23033543
Position Surface form Disambiguated ID Type / Status
Subject Gladsaxe Municipality E573530 entity
Predicate hasSeat P3522 FINISHED
Object Buddinge 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: Buddinge | Statement: [Gladsaxe Municipality, hasSeat, Buddinge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Buddinge
Context triple: [Gladsaxe Municipality, hasSeat, Buddinge]
  • A. Buddinge chosen
    Buddinge is a suburban district in the Copenhagen metropolitan area of Denmark, known for its residential neighborhoods and local commercial center.
  • B. Ordrup
    Ordrup is a suburban residential district in the northern part of Copenhagen, Denmark, known for its affluent neighborhoods and proximity to green areas and the Øresund coast.
  • C. Felsted
    Felsted is a village in Essex, England, known for its historic independent boarding school and rural setting.
  • D. Knudshoved
    Knudshoved is a coastal area on the Danish island of Funen that serves as a key transport hub and former ferry terminal at the western end of the Great Belt crossing.
  • E. Ringsted
    Ringsted is a historic market town and transport hub located in the central part of the Danish island of Zealand.
  • 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_69e245b911188190bc3d96326c847969 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18482e78c8190a89681eec2edb812 completed April 29, 2026, 4:09 a.m.
Created at: April 17, 2026, 3:53 p.m.