Triple

T1992560
Position Surface form Disambiguated ID Type / Status
Subject Weser Uplands E43282 entity
Predicate contains P35 FINISHED
Object Bad Pyrmont E218914 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: Bad Pyrmont | Statement: [Weser Uplands, contains, Bad Pyrmont]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bad Pyrmont
Context triple: [Weser Uplands, contains, Bad Pyrmont]
  • A. Bad Pyrmont chosen
    Bad Pyrmont is a German spa town in Lower Saxony renowned for its mineral springs, historic Kurpark, and long tradition as a health resort.
  • B. Bad Harzburg
    Bad Harzburg is a German spa and resort town on the northern edge of the Harz Mountains, known for its thermal baths, hiking trails, and historic castle ruins.
  • C. Bad Mergentheim
    Bad Mergentheim is a historic spa town in the German state of Baden-Württemberg, renowned for its mineral springs and picturesque setting in the Tauber Valley.
  • D. Bad Dürrenberg
    Bad Dürrenberg is a spa town in the German state of Saxony-Anhalt, known for its saline springs and historic graduation works.
  • E. Bad Tölz
    Bad Tölz is a Bavarian spa town in southern Germany known for its historic old town, alpine scenery, and traditional German architecture.
  • 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_69a88714cf2c819081644be450b8356e completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb86275c88190bed869e9d3cf7ed5 completed March 7, 2026, 5:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae033a39d48190b6389e22de0d4418 completed March 8, 2026, 11:16 p.m.
Created at: March 4, 2026, 7:37 p.m.