Triple

T9472357
Position Surface form Disambiguated ID Type / Status
Subject Sundern E228422 entity
Predicate hasSubdivision P747 FINISHED
Object Langscheid E228423 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: Langscheid | Statement: [Sundern, hasSubdivision, Langscheid]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Langscheid
Context triple: [Sundern, hasSubdivision, Langscheid]
  • A. Langscheid chosen
    Langscheid is a village in the Sauerland region of North Rhine-Westphalia, Germany, known for its scenic setting by the Sorpe Dam and its recreational tourism.
  • B. Hammersbach
    Hammersbach is a village in the Bavarian Alps of Germany that serves as a popular gateway for hiking and mountaineering routes into the nearby mountains, including the Höllental valley.
  • C. Rheydt
    Rheydt is a district of the German city of Mönchengladbach in North Rhine-Westphalia, historically an independent town in the Rhineland.
  • D. Hilchenbach
    Hilchenbach is a small town in the Siegerland region of North Rhine-Westphalia, Germany, known for its wooded hills and proximity to the Rothaar Mountains.
  • E. Eschbach
    Eschbach is a village and district of the town of Usingen in the Hochtaunus region of Hesse, Germany.
  • 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_69ca847162c48190b079076c9595513c completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd7fef6f288190b2d158c829b31de9 completed April 1, 2026, 8:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69d122cd0728819088f6c832cd90d832 completed April 4, 2026, 2:40 p.m.
Created at: March 30, 2026, 7:54 p.m.