Triple

T21592709
Position Surface form Disambiguated ID Type / Status
Subject Plettenberg E532819 entity
Predicate locatedNear P294 FINISHED
Object Herscheid 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: Herscheid | Statement: [Plettenberg, locatedNear, Herscheid]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Herscheid
Context triple: [Plettenberg, locatedNear, Herscheid]
  • A. Herscheid chosen
    Herscheid is a small municipality in the Märkischer Kreis district of North Rhine-Westphalia, Germany.
  • B. Rheintal
    Rheintal is a region in eastern Switzerland along the Rhine River, known for its valleys, towns, and cross-border connections with neighboring countries.
  • C. Emstek
    Emstek is a municipality in Lower Saxony, Germany, situated in the district of Cloppenburg and known for its rural character and agricultural economy.
  • D. De Wolden
    De Wolden is a rural municipality in the northeastern Netherlands known for its scenic landscapes, small villages, and agricultural character.
  • E. Belmbrach
    Belmbrach is a locality or district that forms part of the municipality or area of Roth, likely in Germany.
  • 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_69e0c46251648190876f0427cf2d321b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eefadeb56c8190bce79efadf3c644d completed April 27, 2026, 5:57 a.m.
Created at: April 16, 2026, 6:32 p.m.