Triple
T9498661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neumarkt in der Oberpfalz (district) |
E229077
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object |
Berching
Berching is a historic small town in Bavaria, Germany, known for its well-preserved medieval walls and picturesque old town.
|
E803627
|
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: Berching | Statement: [Neumarkt in der Oberpfalz (district), contains, Berching]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Berching Context triple: [Neumarkt in der Oberpfalz (district), contains, Berching]
-
A.
Aschering
Aschering is a village-level subdivision of the municipality of Pöcking in Bavaria, Germany.
-
B.
Taufkirchen
Taufkirchen is a municipality in Bavaria, Germany, known for its strong aerospace and defense industry presence.
-
C.
Treuchtlingen
Treuchtlingen is a small town in the Bavarian region of Germany, known for its location in the Altmühl Valley and its role as a local railway junction and spa destination.
-
D.
Hildburghausen
Hildburghausen is a town in the German state of Thuringia that historically served as the residence of the dukes of Saxe-Hildburghausen.
-
E.
Vellinghausen
Vellinghausen is a village in western Germany known historically as the site of the Battle of Vellinghausen during the Seven Years' War.
- 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: Berching Triple: [Neumarkt in der Oberpfalz (district), contains, Berching]
Generated description
Berching is a historic small town in Bavaria, Germany, known for its well-preserved medieval walls and picturesque old town.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Berching Target entity description: Berching is a historic small town in Bavaria, Germany, known for its well-preserved medieval walls and picturesque old town.
-
A.
Aschering
Aschering is a village-level subdivision of the municipality of Pöcking in Bavaria, Germany.
-
B.
Taufkirchen
Taufkirchen is a municipality in Bavaria, Germany, known for its strong aerospace and defense industry presence.
-
C.
Treuchtlingen
Treuchtlingen is a small town in the Bavarian region of Germany, known for its location in the Altmühl Valley and its role as a local railway junction and spa destination.
-
D.
Hildburghausen
Hildburghausen is a town in the German state of Thuringia that historically served as the residence of the dukes of Saxe-Hildburghausen.
-
E.
Vellinghausen
Vellinghausen is a village in western Germany known historically as the site of the Battle of Vellinghausen during the Seven Years' War.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd983a94c48190a7ddf95a953c4ecc |
completed | April 1, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d13a0a5ec881908bb1643d2bea2c9f |
completed | April 4, 2026, 4:19 p.m. |
| NEDg | Description generation | batch_69d13b7752fc819094ceb0ade960ecad |
completed | April 4, 2026, 4:25 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d13bc9f0dc8190879c37383b197a3b |
completed | April 4, 2026, 4:26 p.m. |
Created at: March 30, 2026, 7:56 p.m.