Triple

T9605339
Position Surface form Disambiguated ID Type / Status
Subject Eiderstedt E231954 entity
Predicate near P350 FINISHED
Object Friedrichstadt E824154 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: Friedrichstadt | Statement: [Eiderstedt, near, Friedrichstadt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Friedrichstadt
Context triple: [Eiderstedt, near, Friedrichstadt]
  • A. Friedrichstadt chosen
    Friedrichstadt is a historic canal town in northern Germany’s Schleswig-Holstein, known for its Dutch-style architecture and waterways.
  • B. Friedeburg
    Friedeburg is a small municipality in Lower Saxony, Germany, known for its rural character and location within the East Frisian region.
  • C. Schwarmstedt
    Schwarmstedt is a municipality in Lower Saxony, Germany, situated in the Heidekreis district along the River Aller.
  • D. Wallhausen
    Wallhausen is a village in present-day Saxony-Anhalt, Germany, historically notable as the birthplace of Otto I, Holy Roman Emperor.
  • E. Oldenburg
    Oldenburg is a historic European noble house that ruled various territories in Denmark, Norway, and northern Germany and provided numerous monarchs to several European thrones.
  • 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_69ca8484838c8190b2049199d22fef70 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9a5e4a7c8190830b5ad9762ece46 completed April 1, 2026, 10:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1e3f04358819098b2cef9272cbc19 completed April 5, 2026, 4:24 a.m.
Created at: March 30, 2026, 8:08 p.m.