Triple
T12600278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergisches Land |
E300838
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Gummersbach |
E730221
|
NE FINISHED |
How this triple was built (2 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: Gummersbach | Statement: [Bergisches Land, contains, Gummersbach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gummersbach Context triple: [Bergisches Land, contains, Gummersbach]
-
A.
Gummersbach
chosen
Gummersbach is a town in North Rhine-Westphalia, Germany, known as a regional center in the Bergisches Land and a location for higher education and industry.
-
B.
Bergkamen
Bergkamen is a town in North Rhine-Westphalia, Germany, known for its coal mining heritage and post-war planned urban development.
-
C.
Gescher
Gescher is a small town in western Germany’s Münsterland region, noted for its traditional bell foundries and rural character.
-
D.
Radevormwald
Radevormwald is a small historic town in North Rhine-Westphalia, western Germany, known for its hilly Bergisches Land landscape and traditional textile and metalworking industries.
-
E.
Gevelsberg
Gevelsberg is a town in North Rhine-Westphalia, Germany, situated in the Ennepe-Ruhr district within the Ruhr metropolitan region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954d1f6ac8190ab21ca7bcbc80129 |
completed | April 10, 2026, 7:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd7a2796cc81908b6d4cf71f39e88a |
completed | May 8, 2026, 5:52 a.m. |
Created at: April 9, 2026, 5:09 p.m.