Triple

T19692646
Position Surface form Disambiguated ID Type / Status
Subject Lippe (region) E472873 entity
Predicate hasPart P35 FINISHED
Object Barntrup 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: Barntrup | Statement: [Lippe (region), hasPart, Barntrup]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Barntrup
Context triple: [Lippe (region), hasPart, Barntrup]
  • A. Barntrup chosen
    Barntrup is a small town in the Lippe district of North Rhine-Westphalia, Germany, known for its historic architecture and rural surroundings.
  • B. Waldstadt
    Waldstadt is a district of Karlsruhe in the German state of Baden-Württemberg, characterized by its forested setting and primarily residential layout.
  • C. Brenkhausen
    Brenkhausen is a village and district of the town of Höxter in North Rhine-Westphalia, Germany.
  • D. Calmbach
    Calmbach is a small town in Germany’s Black Forest region, known for its scenic location in the Enz Valley and traditional spa and nature tourism.
  • E. Steinbach
    Steinbach is a district or locality that forms part of the town of Hadamar in the German state of Hesse.
  • 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_69d8e515bef88190bc30781aea50537a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e64210cddc8190836faa2996a44457 completed April 20, 2026, 3:11 p.m.
Created at: April 10, 2026, 1:46 p.m.