Triple

T5890721
Position Surface form Disambiguated ID Type / Status
Subject Garding E130980 entity
Predicate locatedWestOf P4239 FINISHED
Object Husum E246172 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: Husum | Statement: [Garding, locatedWestOf, Husum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Husum
Context triple: [Garding, locatedWestOf, 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. 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.
  • D. Pinneberg
    Pinneberg is a town in northern Germany that serves as the administrative center of the district of the same name near Hamburg.
  • E. Wallhausen
    Wallhausen is a village in present-day Saxony-Anhalt, Germany, historically notable as the birthplace of Otto I, Holy Roman Emperor.
  • 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_69c00857439c819095950754176aa58a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c036b228508190b050acf51860a5c2 completed March 22, 2026, 6:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0b14c2ff081908243988d5815be6d completed March 23, 2026, 3:19 a.m.
Created at: March 22, 2026, 3:58 p.m.