Triple

T19738936
Position Surface form Disambiguated ID Type / Status
Subject North Denmark Region E474059 entity
Predicate containsCity P294 FINISHED
Object Pandrup 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: Pandrup | Statement: [North Denmark Region, containsCity, Pandrup]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pandrup
Context triple: [North Denmark Region, containsCity, Pandrup]
  • A. Pandrup chosen
    Pandrup is a small town in northern Jutland, Denmark, known for its rural surroundings and role as a local service and commercial center.
  • B. Haderup
    Haderup is a small town in Denmark, known locally as a rural community that gave its name to the former Aulum-Haderup Municipality.
  • C. Kværndrup
    Kværndrup is a small Danish village on the island of Funen, known for its proximity to the historic Egeskov Castle.
  • D. Knudstrup
    Knudstrup is a small locality in present-day Sweden historically notable as the birthplace of the astronomer Tycho Brahe.
  • E. Knudstrup
    Knudstrup is a locality in Denmark, likely a small village or settlement bearing a traditional Danish place name.
  • 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_69d8e517ebd48190979ee76723bcfadf completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6515f6efc8190a3da113847464399 completed April 20, 2026, 4:16 p.m.
Created at: April 10, 2026, 1:47 p.m.