Triple

T18265475
Position Surface form Disambiguated ID Type / Status
Subject Salem, Baden-Württemberg E437471 entity
Predicate hasSubdivision P747 FINISHED
Object Mittelstenweiler 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: Mittelstenweiler | Statement: [Salem, Baden-Württemberg, hasSubdivision, Mittelstenweiler]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mittelstenweiler
Context triple: [Salem, Baden-Württemberg, hasSubdivision, Mittelstenweiler]
  • A. Mittelstenweiler chosen
    Mittelstenweiler is a former village in southern Germany that now forms part of the municipality of Salem in the state of Baden-Württemberg.
  • B. Neuweiler
    Neuweiler is a small municipality in the Black Forest region of southwestern Germany, known for its rural character and forested landscapes.
  • C. Wülscheid
    Wülscheid is a small locality within the Aegidienberg district of Bad Honnef in North Rhine-Westphalia, Germany.
  • D. Wollmerschied
    Wollmerschied is a small village in the Rheingau region of Hesse, Germany, known as a district of the town of Lorch.
  • E. Niedernhausen
    Niedernhausen is a municipality in the Rheingau-Taunus district of Hesse, Germany, known for its wooded surroundings in the Taunus hills and convenient rail and road links to Wiesbaden and Frankfurt.
  • 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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ff79851481909a4bbeb14fb00647 completed April 19, 2026, 4:14 p.m.
Created at: April 10, 2026, 10:34 a.m.