Triple
T12580911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rüthen |
E300331
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object |
Schneringhausen
Schneringhausen is a locality or district that forms part of the town of Rüthen in North Rhine-Westphalia, Germany.
|
E1077913
|
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: Schneringhausen | Statement: [Rüthen, hasSubdivision, Schneringhausen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schneringhausen Context triple: [Rüthen, hasSubdivision, Schneringhausen]
-
A.
Kneblinghausen
Kneblinghausen is a village and district (Ortsteil) of the town of Rüthen in the Soest district of North Rhine-Westphalia, Germany.
-
B.
Schneppenhausen
Schneppenhausen is a village and district of the town of Weiterstadt in the German state of Hesse.
-
C.
Nennhausen
Nennhausen is a rural municipality in the Havelland district of Brandenburg, Germany, known for its historic manor house and surrounding natural landscapes.
-
D.
Vellinghausen
Vellinghausen is a village in western Germany known historically as the site of the Battle of Vellinghausen during the Seven Years' War.
-
E.
Ochsenhausen
Ochsenhausen is a small historic town in the German state of Baden-Württemberg, best known for its former Benedictine monastery, Ochsenhausen Abbey.
- 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: Schneringhausen Triple: [Rüthen, hasSubdivision, Schneringhausen]
Generated description
Schneringhausen is a locality or district that forms part of the town of Rüthen in North Rhine-Westphalia, Germany.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Schneringhausen Target entity description: Schneringhausen is a locality or district that forms part of the town of Rüthen in North Rhine-Westphalia, Germany.
-
A.
Kneblinghausen
Kneblinghausen is a village and district (Ortsteil) of the town of Rüthen in the Soest district of North Rhine-Westphalia, Germany.
-
B.
Schneppenhausen
Schneppenhausen is a village and district of the town of Weiterstadt in the German state of Hesse.
-
C.
Nennhausen
Nennhausen is a rural municipality in the Havelland district of Brandenburg, Germany, known for its historic manor house and surrounding natural landscapes.
-
D.
Vellinghausen
Vellinghausen is a village in western Germany known historically as the site of the Battle of Vellinghausen during the Seven Years' War.
-
E.
Ochsenhausen
Ochsenhausen is a small historic town in the German state of Baden-Württemberg, best known for its former Benedictine monastery, Ochsenhausen Abbey.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954b97a508190b6c901c506441dd0 |
completed | April 10, 2026, 7:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb63c80048190be87b41cdd4ac775 |
completed | May 7, 2026, 3:56 p.m. |
| NEDg | Description generation | batch_69fcc4fa09448190b662af829712e657 |
completed | May 7, 2026, 4:59 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fcc5d162c081908750fed589ed2d69 |
completed | May 7, 2026, 5:03 p.m. |
Created at: April 9, 2026, 5:02 p.m.