Triple

T23134204
Position Surface form Disambiguated ID Type / Status
Subject Allerød Municipality E577263 entity
Predicate hasAdministrativeCenter P1474 FINISHED
Object Allerød 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: Allerød | Statement: [Allerød Municipality, hasAdministrativeCenter, Allerød]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Allerød
Context triple: [Allerød Municipality, hasAdministrativeCenter, Allerød]
  • A. Allerød chosen
    Allerød is a town in northeastern Zealand, Denmark, known as a suburban community within the Greater Copenhagen area.
  • B. Thyborøn
    Thyborøn is a coastal fishing town and tourist destination in western Jutland, Denmark, known for its harbor, North Sea beaches, and World War II coastal fortifications.
  • C. Haderup
    Haderup is a small town in Denmark, known locally as a rural community that gave its name to the former Aulum-Haderup Municipality.
  • D. Vigerslev
    Vigerslev is a neighborhood within the Valby district of Copenhagen, Denmark, known primarily as a residential area with local amenities and transport links.
  • E. Hardegsen
    Hardegsen is a small town in Lower Saxony, Germany, known for its medieval castle and historic town center.
  • 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_69e245f7b0e481909c473ff4e6a54e2c completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e8ab9b08190969984f8c4494b0f completed April 29, 2026, 4:52 a.m.
Created at: April 17, 2026, 4 p.m.