Triple

T21974986
Position Surface form Disambiguated ID Type / Status
Subject Rhein-Hunsrück-Kreis E542681 entity
Predicate containsTown P847 FINISHED
Object Oberwesel 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: Oberwesel | Statement: [Rhein-Hunsrück-Kreis, containsTown, Oberwesel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oberwesel
Context triple: [Rhein-Hunsrück-Kreis, containsTown, Oberwesel]
  • A. Oberwesel chosen
    Oberwesel is a historic town on the Middle Rhine in Germany, renowned for its well-preserved medieval walls, castles, and picturesque riverside setting.
  • B. Wörth am Rhein
    Wörth am Rhein is a town in the German state of Rhineland-Palatinate, situated on the Rhine River near Karlsruhe and known for its industrial facilities and transport links.
  • C. Merzig
    Merzig is a town in the Saarland region of western Germany, near the borders with France and Luxembourg.
  • D. Kusel
    Kusel is a small town in the German state of Rhineland-Palatinate, known as the administrative center of the Kusel district in the Western Palatinate region.
  • E. Elchingen
    Elchingen is a municipality in southern Germany, historically notable as the site of a major Napoleonic victory during the War of the Third Coalition.
  • 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_69e0c48070988190909db97667b9a0ac completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f12487a1a88190abb8a51fcd533b6a completed April 28, 2026, 9:20 p.m.
Created at: April 16, 2026, 8:03 p.m.