Triple

T22332002
Position Surface form Disambiguated ID Type / Status
Subject Nordfriisk Instituut E552045 entity
Predicate locatedIn P40 FINISHED
Object Husum 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: Husum | Statement: [Nordfriisk Instituut, locatedIn, Husum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Husum
Context triple: [Nordfriisk Instituut, locatedIn, Husum]
  • A. Husum chosen
    Husum is a small coastal town in northern Germany known for its North Sea harbor, maritime heritage, and role as a local cultural and commercial center.
  • B. Itzehoe
    Itzehoe is a historic town in northern Germany known for its medieval origins and role as a regional center in the state of Schleswig-Holstein.
  • C. Himmerich
    Himmerich is a hill in Germany’s Siebengebirge range, known for its forested slopes and hiking trails overlooking the Rhine valley.
  • D. Aurich
    Aurich is a historic town in northwestern Germany that serves as one of the principal urban centers of the East Frisia region in Lower Saxony.
  • E. Geesthacht
    Geesthacht is a town in northern Germany known for its location on the Elbe River and its energy research and industrial facilities.
  • 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_69e11e482f788190b78d1588fc26d606 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1577b555c8190ac61c026ee7dfb2b completed April 29, 2026, 12:57 a.m.
Created at: April 16, 2026, 8:43 p.m.