Triple
T18127934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weißenburg-Gunzenhausen district |
E433929
|
entity |
| Predicate | containsMunicipality |
P852
|
FINISHED |
| Object |
Theilenhofen
Theilenhofen is a small rural municipality in the Bavarian region of southern Germany.
|
E1334191
|
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: Theilenhofen | Statement: [Weißenburg-Gunzenhausen district, containsMunicipality, Theilenhofen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Theilenhofen Context triple: [Weißenburg-Gunzenhausen district, containsMunicipality, Theilenhofen]
-
A.
Reichertshofen
Reichertshofen is a market town and municipality in Upper Bavaria, Germany, known for its location near the confluence of the Paar and Ilm rivers and its proximity to the city of Ingolstadt.
-
B.
Wehofen
Wehofen is a district of the Walsum area in the city of Duisburg in North Rhine-Westphalia, Germany.
-
C.
Odelshofen
Odelshofen is a village and district (Ortsteil) of the town of Kehl in the state of Baden-Württemberg, Germany.
-
D.
Gerolzhofen
Gerolzhofen is a small historic town in northern Bavaria, Germany, known for its medieval architecture and wine-growing surroundings.
-
E.
Diedenhofen
Diedenhofen is the historical German name for the town of Thionville in northeastern France, near the border with Luxembourg and Germany.
- 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: Theilenhofen Triple: [Weißenburg-Gunzenhausen district, containsMunicipality, Theilenhofen]
Generated description
Theilenhofen is a small rural municipality in the Bavarian region of southern Germany.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Theilenhofen Target entity description: Theilenhofen is a small rural municipality in the Bavarian region of southern Germany.
-
A.
Reichertshofen
Reichertshofen is a market town and municipality in Upper Bavaria, Germany, known for its location near the confluence of the Paar and Ilm rivers and its proximity to the city of Ingolstadt.
-
B.
Wehofen
Wehofen is a district of the Walsum area in the city of Duisburg in North Rhine-Westphalia, Germany.
-
C.
Odelshofen
Odelshofen is a village and district (Ortsteil) of the town of Kehl in the state of Baden-Württemberg, Germany.
-
D.
Gerolzhofen
Gerolzhofen is a small historic town in northern Bavaria, Germany, known for its medieval architecture and wine-growing surroundings.
-
E.
Diedenhofen
Diedenhofen is the historical German name for the town of Thionville in northeastern France, near the border with Luxembourg and Germany.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddef4cd88190b16ef0d6ed3968c6 |
completed | April 19, 2026, 1:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a050d5e28208190b3ddd112e6e36b4d |
completed | May 13, 2026, 11:46 p.m. |
| NEDg | Description generation | batch_6a050e12c29c8190b4be001f9fc8dd05 |
completed | May 13, 2026, 11:49 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a050ecc33e48190bc28430a6a771492 |
completed | May 13, 2026, 11:52 p.m. |
Created at: April 10, 2026, 10:29 a.m.