Triple

T10947468
Position Surface form Disambiguated ID Type / Status
Subject Marktplatz Goslar E258634 entity
Predicate locatedIn P40 FINISHED
Object Goslar E51097 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: Goslar | Statement: [Marktplatz Goslar, locatedIn, Goslar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Goslar
Context triple: [Marktplatz Goslar, locatedIn, Goslar]
  • A. Goslar chosen
    Goslar is a historic German town at the foot of the Harz Mountains, renowned for its well-preserved medieval old town and former silver mines, both recognized as UNESCO World Heritage Sites.
  • B. Lemgo
    Lemgo is a historic town in the Lippe district of North Rhine-Westphalia, Germany, known for its well-preserved medieval architecture and Hanseatic heritage.
  • C. Boppard
    Boppard is a historic town on the Rhine River in Germany, renowned for its well-preserved medieval architecture, wine culture, and scenic river landscapes.
  • D. Meppen
    Meppen is a historic town in Lower Saxony, Germany, known as a regional center in the Emsland district near the Dutch border.
  • E. Fritzlar
    Fritzlar is a historic town in northern Hesse, Germany, known for its well-preserved medieval old town and its significance in early German Christian history.
  • 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_69d6aa8769b4819082bfe5e61b9017f0 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d770ebac3c8190849ddda3d9d37327 completed April 9, 2026, 9:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69e5099f57ac81909e7734b83ad96a40 completed April 19, 2026, 4:58 p.m.
Created at: April 8, 2026, 9:23 p.m.