Triple

T23089467
Position Surface form Disambiguated ID Type / Status
Subject Blomberg (Lippe) E575703 entity
Predicate hasSubdivision P747 FINISHED
Object Lüdenhausen
Lüdenhausen is a village and district of the town of Blomberg in the Lippe region of North Rhine-Westphalia, Germany.
E1576569 NE FINISHED

How this triple was built (4 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: Lüdenhausen | Statement: [Blomberg (Lippe), hasSubdivision, Lüdenhausen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lüdenhausen
Context triple: [Blomberg (Lippe), hasSubdivision, Lüdenhausen]
  • A. Thannhausen
    Thannhausen is a small town in the Bavarian region of Swabia in southern Germany.
  • B. Nennhausen
    Nennhausen is a rural municipality in the Havelland district of Brandenburg, Germany, known for its historic manor house and surrounding natural landscapes.
  • C. Leutershausen
    Leutershausen is a historic small town in Bavaria, Germany, known for its well-preserved medieval character and traditional Franconian architecture.
  • D. Völlinghausen
    Völlinghausen is a village within the municipality of Möhnesee in North Rhine-Westphalia, Germany.
  • E. Fahrenzhausen
    Fahrenzhausen is a municipality in Upper Bavaria, Germany, situated north of Munich along the Amper River.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Lüdenhausen
Triple: [Blomberg (Lippe), hasSubdivision, Lüdenhausen]
Generated description
Lüdenhausen is a village and district of the town of Blomberg in the Lippe region of North Rhine-Westphalia, Germany.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Lüdenhausen
Target entity description: Lüdenhausen is a village and district of the town of Blomberg in the Lippe region of North Rhine-Westphalia, Germany.
  • A. Thannhausen
    Thannhausen is a small town in the Bavarian region of Swabia in southern Germany.
  • B. Nennhausen
    Nennhausen is a rural municipality in the Havelland district of Brandenburg, Germany, known for its historic manor house and surrounding natural landscapes.
  • C. Leutershausen
    Leutershausen is a historic small town in Bavaria, Germany, known for its well-preserved medieval character and traditional Franconian architecture.
  • D. Völlinghausen
    Völlinghausen is a village within the municipality of Möhnesee in North Rhine-Westphalia, Germany.
  • E. Fahrenzhausen
    Fahrenzhausen is a municipality in Upper Bavaria, Germany, situated north of Munich along the Amper River.
  • F. None of above. chosen

Provenance (5 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_69e245bf3e3c819086d3448720efc01b completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18da8818481908d768a0462f3f837 completed April 29, 2026, 4:48 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0c3f35955081908a28f2e5925a28ab completed May 19, 2026, 10:45 a.m.
NEDg Description generation batch_6a0c4008c4a881908ad49e733b549036 completed May 19, 2026, 10:48 a.m.
NED2 Entity disambiguation (via description) batch_6a0c40c6562481908689eca2a4997115 completed May 19, 2026, 10:51 a.m.
Created at: April 17, 2026, 3:57 p.m.