Triple
T14306626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marbach am Neckar |
E354713
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object |
Rielingshausen
Rielingshausen is a village and district of the town of Marbach am Neckar in the German state of Baden-Württemberg.
|
E1163051
|
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: Rielingshausen | Statement: [Marbach am Neckar, hasSubdivision, Rielingshausen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rielingshausen Context triple: [Marbach am Neckar, hasSubdivision, Rielingshausen]
-
A.
Nennhausen
Nennhausen is a rural municipality in the Havelland district of Brandenburg, Germany, known for its historic manor house and surrounding natural landscapes.
-
B.
Willingshausen
Willingshausen is a small municipality in central Germany known for its historic artists’ colony and rural cultural heritage.
-
C.
Vellinghausen
Vellinghausen is a village in western Germany known historically as the site of the Battle of Vellinghausen during the Seven Years' War.
-
D.
Ehringshausen
Ehringshausen is a municipality in the Lahn-Dill district of the German state of Hesse.
-
E.
Rüdinghausen
Rüdinghausen is a district of the city of Witten in North Rhine-Westphalia, Germany, characterized by its residential areas and local amenities.
- 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: Rielingshausen Triple: [Marbach am Neckar, hasSubdivision, Rielingshausen]
Generated description
Rielingshausen is a village and district of the town of Marbach am Neckar in the German state of Baden-Württemberg.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Rielingshausen Target entity description: Rielingshausen is a village and district of the town of Marbach am Neckar in the German state of Baden-Württemberg.
-
A.
Nennhausen
Nennhausen is a rural municipality in the Havelland district of Brandenburg, Germany, known for its historic manor house and surrounding natural landscapes.
-
B.
Willingshausen
Willingshausen is a small municipality in central Germany known for its historic artists’ colony and rural cultural heritage.
-
C.
Vellinghausen
Vellinghausen is a village in western Germany known historically as the site of the Battle of Vellinghausen during the Seven Years' War.
-
D.
Ehringshausen
Ehringshausen is a municipality in the Lahn-Dill district of the German state of Hesse.
-
E.
Rüdinghausen
Rüdinghausen is a district of the city of Witten in North Rhine-Westphalia, Germany, characterized by its residential areas and local amenities.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b156b0819083f2bd319deed1b6 |
completed | April 14, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff453e3d3081909f6b6e8b67a824ac |
completed | May 9, 2026, 2:31 p.m. |
| NEDg | Description generation | batch_69ff46e4771881909f1dc8c9d5e7e411 |
completed | May 9, 2026, 2:38 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ff471fe76081909189dc5f1e2453e6 |
completed | May 9, 2026, 2:39 p.m. |
Created at: April 10, 2026, 1:12 a.m.