Triple

T19692645
Position Surface form Disambiguated ID Type / Status
Subject Lippe (region) E472873 entity
Predicate hasPart P35 FINISHED
Object Schieder-Schwalenberg 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: Schieder-Schwalenberg | Statement: [Lippe (region), hasPart, Schieder-Schwalenberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schieder-Schwalenberg
Context triple: [Lippe (region), hasPart, Schieder-Schwalenberg]
  • A. Schieder-Schwalenberg chosen
    Schieder-Schwalenberg is a small town in the Lippe district of North Rhine-Westphalia, Germany, known for its historic architecture and scenic location in the Teutoburg Forest region.
  • B. Wülscheid
    Wülscheid is a small locality within the Aegidienberg district of Bad Honnef in North Rhine-Westphalia, Germany.
  • C. Bodersweier
    Bodersweier is a village and district of the town of Kehl in the Ortenaukreis region of Baden-Württemberg, Germany.
  • D. Schneringhausen
    Schneringhausen is a locality or district that forms part of the town of Rüthen in North Rhine-Westphalia, Germany.
  • E. Niederfeld
    Niederfeld is a district within the Mannheim borough of Neckarau in the German state of Baden-Württemberg.
  • 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.